From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: Running 2 process on the same machine Date: Mon, 14 Nov 2016 15:44:57 +0000 Message-ID: <20161114154456.GA246236@bricha3-MOBL3.ger.corp.intel.com> References: <60A9A962-53C9-4050-8D84-74AD13CCE09B@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "Wiles, Keith" , "dev@dpdk.org" To: Keren Hochman Return-path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id E58CA47D1 for ; Mon, 14 Nov 2016 16:45:00 +0100 (CET) Content-Disposition: inline In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Tue, Nov 08, 2016 at 02:02:32PM +0200, Keren Hochman wrote: > Also, I can't understand how to define socket-mem. I did not see anything > related to hugepages in /etc/sysctl.conf. Can i mount hugepages to 2 > different dirs instead and use --huge-dir ? > Thank you. > Doing so would be a replacement for using the --file-prefix option, because even with two different hugepage mount points all pages can be used via each one, meaning the first process can still use all hugepage memory. The only exception to this that I know of is if the two mountpoints are for two different sizes of hugepages. With regards to the process failing if you use the --no-huge option: did you try running with --no-huge and a -m or --socket-mem option? By default, I think the --no-huge option only allocates a relatively small amount of memory for DPDK use. Try "--no-huge -m 2048" and see if that helps. Regards, /Bruce