From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by orsmga102.jf.intel.com with ESMTP; 14 Nov 2016 07:44:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,491,1473145200"; d="scan'208";a="30845025" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.64]) by orsmga004.jf.intel.com with SMTP; 14 Nov 2016 07:44:57 -0800 Received: by (sSMTP sendmail emulation); Mon, 14 Nov 2016 15:44:57 +0000 Date: Mon, 14 Nov 2016 15:44:57 +0000 From: Bruce Richardson To: Keren Hochman Cc: "Wiles, Keith" , "dev@dpdk.org" 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 Content-Disposition: inline In-Reply-To: Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.7.1 (2016-10-04) Subject: Re: [dpdk-dev] Running 2 process on the same machine 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: Mon, 14 Nov 2016 15:45:01 -0000 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