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 92B87DE3; Mon, 12 Jun 2017 16:25:23 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2017 07:25:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,333,1493708400"; d="scan'208";a="113849126" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.28]) by fmsmga006.fm.intel.com with SMTP; 12 Jun 2017 07:25:20 -0700 Received: by (sSMTP sendmail emulation); Mon, 12 Jun 2017 15:25:19 +0100 Date: Mon, 12 Jun 2017 15:25:19 +0100 From: Bruce Richardson To: Marco Varlese Cc: "users@dpdk.org" , dev@dpdk.org Message-ID: <20170612142519.GC67396@bricha3-MOBL3.ger.corp.intel.com> References: <1497276908.3084.37.camel@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1497276908.3084.37.camel@suse.com> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.8.1 (2017-04-11) Subject: Re: [dpdk-dev] Problem with MBUF pool allocation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Jun 2017 14:25:24 -0000 On Mon, Jun 12, 2017 at 04:15:08PM +0200, Marco Varlese wrote: > Hi, > I'm seeing an error reported by the DPDK EAL when allocating the MBUF pools. > > The error is: > "MBUF: error setting mempool handler" > > I have a multi-node NUMA system and I get the exact same error when trying to > allocate the memory from the different nodes.  > > The bootstrap parameters I use to reserve huge-pages are: > "default_hugepagesz=1G hugepagesz=1G hugepages=32" > > If I check the available huge-pages in my systems they look Ok (see below). > fromm:~/:[130]# cat /proc/meminfo  > > Any idea / help would be much appreciated. > > > Thanks, > Marco > Hi Marco, in recent releases the mempools are now based on different mempool drivers, rather than just being a single mempool library. So if this is a shared library build, you may need to pass in "-d /path/to/driver" parameter to make sure the default mempool driver is picked up by the EAL. Regards, /Bruce