Incorrect amount of 2M hugepages deployed when dpdk is enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
Fuel Sustaining |
Bug Description
When hugepages and dpdk is enabled, the actual amount of created 2.0MB hugepages does not match with the amount configured in fuel under node attributes.
It seems that the actual value is the sum of the configured value and the memory configured for DPDK Huge Pages.
Example:
Fuel node attributes as follows (see also attached screen shot)
Nova huge pages
Size Count
2.0MB 2048
1.0GB 10
DPDK Huge Pages 1024 DPDK Huge Pages per NUMA node in MB
After deployment we see 3072 2.0MB hugepages and 10 1.0GB hugepages
# cat /sys/kernel/
3072
# cat /sys/kernel/
10
Which fits the the generated /etc/default/grub file:
GRUB_CMDLINE_
The DPDK uses one 1.0GB huge pages:
grep huge /proc/*/numa_maps
/proc/944684/
/proc/944684/
Changed in fuel: | |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
milestone: | none → 9.2 |
importance: | Undecided → High |
Changed in fuel: | |
milestone: | 9.2 → 9.3 |
Changed in fuel: | |
status: | Incomplete → Invalid |
Please attach diagnostic snapshot, marking as Incomplete.