From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by dpdk.org (Postfix) with ESMTP id 591718DAB for ; Thu, 1 Oct 2015 00:04:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9672; q=dns/txt; s=iport; t=1443650679; x=1444860279; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=CwHGpEfOF6lZ5yS4wysw0CPfwQXs3Q0Zz0Me4y9S5GA=; b=A2/zWMiTjjIAT4FWk9vuukcx3dlb2bCykYqBdjT4wEiBu1bzkx7wNbUo Fr+oi7fKjhiiiXLbbGifOGltDeLs4n+nJ9z5t2D0//9/Clwyh9/KoBpLL +H+vSqr9uG6OEwYAFxynHFIHqAhgH1Vv+ADbZpNnvpMx9tTfX2PFPiVkW o=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0AcAgBBWwxW/4kNJK1egldNVG0GhA65XgENgXuFeQKBOjgUAQEBAQEBAYEKhCQBAQEEeQwEAgEIEQMBAQEoBzIUCQgCBAENBYguDct9AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4twhHwRBwaEJgWSRoMyAYUVh32BT0aHE5IoHwEBQoIRHYFUcYh1gQUBAQE X-IronPort-AV: E=Sophos;i="5.17,614,1437436800"; d="scan'208,217";a="31540124" Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-9.cisco.com with ESMTP; 30 Sep 2015 22:04:37 +0000 Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t8UM4b9v012831 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 30 Sep 2015 22:04:37 GMT Received: from xch-aln-016.cisco.com (173.36.7.26) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 30 Sep 2015 17:04:37 -0500 Received: from xhc-aln-x01.cisco.com (173.36.12.75) by xch-aln-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Wed, 30 Sep 2015 17:04:37 -0500 Received: from xmb-aln-x03.cisco.com ([169.254.6.63]) by xhc-aln-x01.cisco.com ([173.36.12.75]) with mapi id 14.03.0248.002; Wed, 30 Sep 2015 17:04:36 -0500 From: "shesha Sreenivasamurthy (shesha)" To: "Ananyev, Konstantin" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] Unlinking hugepage backing file after initialiation Thread-Index: AQHQ+kpckJG1vBipX0G0rq8U7ayRsJ5ThlyAgAB9RAD//6TIgIAAtHgAgAEfX4CAAHfygP//jayA Date: Wed, 30 Sep 2015 22:04:36 +0000 Message-ID: References: <20150929161628.GA3810@redhat.com> <20150930003531-mutt-send-email-mst@redhat.com> <2601191342CEEE43887BDE71AB97725836AA21E7@irsmsx105.ger.corp.intel.com> In-Reply-To: <2601191342CEEE43887BDE71AB97725836AA21E7@irsmsx105.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [173.37.102.26] MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 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 22:04:40 -0000 My bad that I said its not working, apologies. Isn=92t it correct to say that single process application do not benefit fr= om having backing files ? In that case can make this configurable by passin= g a command line argument that will either unlink or keep the backing files= , defaulting it to keeping the backing files. Single process application to= do not need these files around can pass additional param to unlink these f= iles ? -- - Thanks char * (*shesha) (uint64_t cache, uint8_t F00D) { return 0x0000C0DE; } From: "Ananyev, Konstantin" > Date: Wednesday, September 30, 2015 at 2:53 PM To: Cisco Employee >, "dev@dpdk.o= rg" > Cc: "Michael S. Tsirkin" > Subject: RE: [dpdk-dev] Unlinking hugepage backing file after initialiation -----Original Message----- From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of shesha Sreenivasamurth= y (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 initialiation What I heard is the following: A multi-process DPDK application, working ei= ther in master-worker or master-slave fashion, can potentially benefit by keeping the backing files in hugetlbfs. However, it = 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 On the other hand, for a single process application there is actually no be= nefit keeping the pages around. Therefore, I was wondering if we can make this configurable by passing a co= mmand line argument that will either unlink or keep the backing files. -- - Thanks char * (*shesha) (uint64_t cache, uint8_t F00D) { return 0x0000C0DE; } From: "Michael S. Tsirkin" > Date: Tuesday, September 29, 2015 at 2:35 PM To: Cisco Employee > Cc: "Xie, Huawei" >, "dev@dpdk.org" > Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiation 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 ? AFAIK qemu unlinks them already. -- MST