From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 575] Hugepages backing file map0 is not being unlinked
Date: Tue, 10 Nov 2020 15:09:23 +0000 [thread overview]
Message-ID: <bug-575-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=575
Bug ID: 575
Summary: Hugepages backing file map0 is not being unlinked
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: michallinuxstuff@gmail.com
Target Milestone: ---
I am not sure if this is a bug or simply part of the design so please, bear
with me. :)
I noticed that whenever application - which uses DPDK's mem components for
mapping hugepages - exits there's always one hugepages backing file left under
hugetlbfs mount. Specifically, it's the file that's mapped under the very
begging of the address space. E.g. where base-virtaddr is set to
0x200000000000:
200000200000-200000400000 rw-s 00000000 00:29 18115803
/dev/hugepages/spdk_pid1806446map_0
When the unlinking starts upon existing, everything down to map1
(0x200000400000) is unlinked but map0 remains. This is not the case when
--huge-unlink is used during the init part (all backing files are unlinked at
the start then, including map0).
This doesn't seem to be a big deal in itself, but depending on what size of
hugepages we are using this may leave different footprint (e.g. we start 3 apps
simultaneously, each one uses 1G hugepages. When they all exit, 3G of hugepages
may be still in use). I can see that there's also a cleanup routine which is
fired upon starting the app, to make sure that any lingering backing files are
removed, but still. :)
Any hints on why this might be the case would be appreciated. :)
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-11-10 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-575-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).