From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 9734E12A8 for ; Tue, 29 Sep 2015 11:03:18 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 29 Sep 2015 02:03:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,607,1437462000"; d="scan'208";a="799488682" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga001.fm.intel.com with ESMTP; 29 Sep 2015 02:03:16 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.252]) by IRSMSX102.ger.corp.intel.com ([169.254.2.160]) with mapi id 14.03.0248.002; Tue, 29 Sep 2015 10:03:16 +0100 From: "Ananyev, Konstantin" To: "shesha Sreenivasamurthy (shesha)" , "dev@dpdk.org" Thread-Topic: Unlinking hugepage backing file after initialiation Thread-Index: AQHQ+kpckJG1vBipX0G0rq8U7ayRsJ5TNnug Date: Tue, 29 Sep 2015 09:03:15 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836AA13EA@irsmsx105.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2015 09:03:19 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of shesha Sreenivasamur= thy (shesha) > Sent: Tuesday, September 29, 2015 1:04 AM > To: dev@dpdk.org > Subject: [dpdk-dev] Unlinking hugepage backing file after initialiation >=20 > Hello, > As of DPDK2.1, backing files are created in hugetablefs during mapping (i= n eal_memory.c::rte_eal_hugepage_init()) and these files are > not cleaned up (unlinked) after initialization (mmap-ing). This means, wh= en the application crashes or stopped, the memory is still > consumed. Therefore, is there any reason not to unlink backing files afte= r initialization=20 For secondary process(es) to be able to open/map them too? Konstantin >? If no, I will send a patch for the change. >=20 > -- > - Thanks > char * (*shesha) (uint64_t cache, uint8_t F00D) > { return 0x0000C0DE; }