Bug 575
Summary: | Hugepages backing file map0 is not being unlinked | ||
---|---|---|---|
Product: | DPDK | Reporter: | mberger (michallinuxstuff) |
Component: | core | Assignee: | mberger (michallinuxstuff) |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | ajit.khaparde, anatoly.burakov |
Priority: | Normal | ||
Version: | 20.11 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All |
Description
mberger
2020-11-10 16:09:23 CET
It depends, but most likely reason for this is a memory leak of some sort. Generally, when primary process deinitializes, not everything gets unmapped because the expectation is that other processes might still be active and keep references to some of that memory. Additionally, some things may intentionally leak memory (e.g. RX callbacks in ethdev) because it is generally impossible to not leak it safely. I would advise adding a rte_malloc_heap_dump() call right after rte_eal_cleanup() and see if anything is still allocated - that's usually the reason why the first page isn't unmapped. Can you try Anatoly's suggestion? |