From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] app/testpmd: adds mlockall() to fix pages Date: Wed, 13 Sep 2017 11:39:45 +0200 Message-ID: <4147502.SWF1kaKTU5@xps> References: <22990026376b08418cb0eb6f028840c03e89f47f.1505221429.git.echaudro@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, jingjing.wu@intel.com To: Eelco Chaudron Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 589BC199B4 for ; Wed, 13 Sep 2017 11:39:46 +0200 (CEST) In-Reply-To: <22990026376b08418cb0eb6f028840c03e89f47f.1505221429.git.echaudro@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" 12/09/2017 15:08, Eelco Chaudron: > 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. Does it work on FreeBSD? Is there any drawback? Do we need to add an option for it?