From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 424B1A04DB; Tue, 10 Nov 2020 16:09:28 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 2BE6FF90; Tue, 10 Nov 2020 16:09:26 +0100 (CET) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id C832AF64 for ; Tue, 10 Nov 2020 16:09:24 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id 9D140A04DD; Tue, 10 Nov 2020 16:09:23 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Tue, 10 Nov 2020 15:09:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 20.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: michallinuxstuff@gmail.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 575] Hugepages backing file map0 is not being unlinked X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D575 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 un= der 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 hugep= ages 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. :) --=20 You are receiving this mail because: You are the assignee for the bug.=