From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id AEEC08DA6 for ; Wed, 30 Sep 2015 23:53:48 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP; 30 Sep 2015 14:53:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,614,1437462000"; d="scan'208";a="571636940" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by FMSMGA003.fm.intel.com with ESMTP; 30 Sep 2015 14:53:46 -0700 Received: from irsmsx105.ger.corp.intel.com ([169.254.7.252]) by IRSMSX108.ger.corp.intel.com ([169.254.11.107]) with mapi id 14.03.0248.002; Wed, 30 Sep 2015 22:53:45 +0100 From: "Ananyev, Konstantin" To: "shesha Sreenivasamurthy (shesha)" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Unlinking hugepage backing file after initialiation Thread-Index: AQHQ+kpckJG1vBipX0G0rq8U7ayRsJ5ThlyAgAAYrwCAABoiAIAAPx4AgAGUuoCAABIUMA== Date: Wed, 30 Sep 2015 21:53:45 +0000 Message-ID: <2601191342CEEE43887BDE71AB97725836AA21E7@irsmsx105.ger.corp.intel.com> References: <20150929161628.GA3810@redhat.com> <20150930003531-mutt-send-email-mst@redhat.com> 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.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "Michael S. Tsirkin" 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: Wed, 30 Sep 2015 21:53:49 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of shesha Sreenivasamur= thy (shesha) > Sent: Wednesday, September 30, 2015 10:44 PM > To: dev@dpdk.org > Cc: Michael S. Tsirkin > Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiati= on >=20 > What I heard is the following: A multi-process DPDK application, working = either in master-worker or master-slave fashion, can > potentially benefit by keeping the backing files in hugetlbfs. However, i= t is does not work today as the pages are cleaned and added > back when the application restarts. Who says it is not working? I admit that DPDK MP model is probably a bit constrained, but it does work. It is probably good to read some docs: http://dpdk.org/doc/guides/prog_guide/multi_proc_support.html and/or look at the code that does MP support inside DPDK. I think that might make things clearer. Konstantin=20 > On the other hand, for a single process application there is actually no = benefit keeping the pages > around. >=20 > Therefore, I was wondering if we can make this configurable by passing a = command line argument that will either unlink or keep the > backing files. >=20 > -- > - Thanks > char * (*shesha) (uint64_t cache, uint8_t F00D) > { return 0x0000C0DE; } >=20 > From: "Michael S. Tsirkin" > > Date: Tuesday, September 29, 2015 at 2:35 PM > To: Cisco Employee > > Cc: "Xie, Huawei" >, "d= ev@dpdk.org" > > > Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiati= on >=20 > On Tue, Sep 29, 2015 at 05:50:00PM +0000, shesha Sreenivasamurthy (shesha= ) wrote: > Sure. Then, is there any real reason why the backing files should not be > unlinked ? >=20 > AFAIK qemu unlinks them already. >=20 > -- > MST