From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergio Gonzalez Monroy Subject: Re: [PATCH] app/testpmd: adds mlockall() to fix pages Date: Fri, 29 Sep 2017 10:27:43 +0100 Message-ID: <00ad8865-a782-07cb-2ade-1cfec2cb456a@intel.com> References: <22990026376b08418cb0eb6f028840c03e89f47f.1505221429.git.echaudro@redhat.com> <7ca2adec-cb72-ea15-8c4b-ae33b8889036@intel.com> <2915a386-08ad-ca2e-4b33-2c001ec6c7dc@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: echaudro@redhat.com, jingjing.wu@intel.com Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 9A8541B21D for ; Fri, 29 Sep 2017 11:27:46 +0200 (CEST) In-Reply-To: <2915a386-08ad-ca2e-4b33-2c001ec6c7dc@redhat.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 29/09/2017 09:15, Eelco Chaudron wrote: > On 29/09/17 10:07, Sergio Gonzalez Monroy wrote: >> On 12/09/2017 14:08, Eelco Chaudron wrote: >>> Call the mlockall() function, to attempt to lock all of its process >>> memory into physical RAM, and preventing the kernel from paging any >>> of its memory to disk. >>> >>> When using testpmd for performance testing, depending on the code path >>> taken, we see a couple of page faults in a row. These faults effect >>> the overall drop-rate of testpmd. On Linux the mlockall() call will >>> prefault all the pages of testpmd (and the DPDK libraries if linked >>> dynamically), even without LD_BIND_NOW. >>> >>> Signed-off-by: Eelco Chaudron >>> --- >> >> When used for performance testing using hugepages or --no-huge option? > This is independent of huge pages, its for the text (code) sections. Understood. Just for curiosity, how much drop-rate was observed? Thanks, Sergio