From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 7868D3787 for ; Tue, 29 Sep 2015 13:14:32 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP; 29 Sep 2015 04:14:31 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,607,1437462000"; d="scan'208";a="815372224" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.61]) by orsmga002.jf.intel.com with SMTP; 29 Sep 2015 04:14:30 -0700 Received: by (sSMTP sendmail emulation); Tue, 29 Sep 2015 12:14:29 +0025 Date: Tue, 29 Sep 2015 12:14:28 +0100 From: Bruce Richardson To: "Ananyev, Konstantin" Message-ID: <20150929111428.GB6748@bricha3-MOBL3> References: <2601191342CEEE43887BDE71AB97725836AA13EA@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2601191342CEEE43887BDE71AB97725836AA13EA@irsmsx105.ger.corp.intel.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" 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 11:14:32 -0000 On Tue, Sep 29, 2015 at 09:03:15AM +0000, Ananyev, Konstantin wrote: > > > > -----Original Message----- > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of shesha Sreenivasamurthy (shesha) > > Sent: Tuesday, September 29, 2015 1:04 AM > > To: dev@dpdk.org > > Subject: [dpdk-dev] Unlinking hugepage backing file after initialiation > > > > Hello, > > As of DPDK2.1, backing files are created in hugetablefs during mapping (in eal_memory.c::rte_eal_hugepage_init()) and these files are > > not cleaned up (unlinked) after initialization (mmap-ing). This means, when the application crashes or stopped, the memory is still > > consumed. Therefore, is there any reason not to unlink backing files after initialization > > For secondary process(es) to be able to open/map them too? > Konstantin > Exactly. The hugepages are kept present on the file system so that secondary processes can use them to attach to a primary process memory in a multi-process setup. What is done instead is that any old hugepage files are cleaned up when the application starts (or restarts). Regards, /Bruce > >? If no, I will send a patch for the change. > > > > -- > > - Thanks > > char * (*shesha) (uint64_t cache, uint8_t F00D) > > { return 0x0000C0DE; }