dpdk fails to use 1G huge pages depending on the available mountpoints
Bug #1557532 reported by
Christian Ehrhardt
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dpdk (Ubuntu) |
Fix Released
|
Medium
|
Christian Ehrhardt |
Bug Description
EAL: 6 hugepages of size 1073741824 reserved, but no mounted hugetlbfs found for that size
EAL: No free hugepages reported in hugepages-2048kB
That can happen if:
- one configures ONLY 1G pages
and
- the default hugepage size is not 1G
That would be a lack of our dpdk-init script, but actually even when mounting a 1G mountpoint it fails.
It needs to be debugged in what way it expects a non-default size hugepage mount and then provided by dpdk init scripts OR fixed in dpdk code.
Changed in dpdk (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
assignee: | nobody → ChristianEhrhardt (paelzer) |
milestone: | none → ubuntu-16.04 |
To post a comment you must log in.
Check code
opens /proc/mounts
gets pagesz_str defining what the mountpoint has
if nothing is set assume default size
if something is set in the mp's options calculate the size
check if this is the mountpoint matching
=> not working for my mountpoint
Need to be run in gdb, to check where exactly it is failing