Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • VILLASnode VILLASnode
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ACS
  • Public
  • VILLASframework
  • VILLASnodeVILLASnode
  • Issues
  • #294

Closed
Open
Created Jun 08, 2021 by Juan Noreña@jpnorenamReporter

Using hugepages in a docker container

Hi @stvogel,

Running a conteneraized image of villas in a kubernetes cluster with hugepages configuration results in a process dumped when allocating memory using hugetbl. It may depend on the memory backing configuration for the virtualization used (kvm/qemu libvirt in my case). However, checking cat /proc/meminfo | grep Huge the HugePages_Total seems to be correctly locked by villas.

Cheers.

Edited Jun 08, 2021 by Juan Noreña
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking