From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 0BCDA2E8A for ; Wed, 12 Apr 2017 12:32:43 +0200 (CEST) Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Apr 2017 03:32:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,190,1488873600"; d="scan'208";a="87802554" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by fmsmga005.fm.intel.com with ESMTP; 12 Apr 2017 03:32:41 -0700 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.12]) by IRSMSX153.ger.corp.intel.com ([163.33.192.75]) with mapi id 14.03.0319.002; Wed, 12 Apr 2017 11:32:40 +0100 From: "Ananyev, Konstantin" To: Shreyansh Jain , "Richardson, Bruce" CC: Thomas Monjalon , john miller , "dev@dpdk.org" , "olivier.matz@6wind.com" Thread-Topic: [dpdk-dev] error in testpmd when CONFIG_RTE_BUILD_SHARED_LIB=y Thread-Index: AQHSsu3sIfIeq8nFrUS0Gna/tJruBqHAfO2AgACdtYCAAFdWAIAABcyAgAASDMA= Date: Wed, 12 Apr 2017 10:32:39 +0000 Message-ID: <2601191342CEEE43887BDE71AB9772583FAE812F@IRSMSX109.ger.corp.intel.com> References: <357262EF-AA7B-4064-963E-FF130E4607E6@atomicrules.com> <1675520.qVeAGBHxLM@xps13> <20170412100521.GB20092@bricha3-MOBL3.ger.corp.intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] error in testpmd when CONFIG_RTE_BUILD_SHARED_LIB=y 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: Wed, 12 Apr 2017 10:32:44 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Shreyansh Jain > Sent: Wednesday, April 12, 2017 11:26 AM > To: Richardson, Bruce > Cc: Thomas Monjalon ; john miller ; dev@dpdk.org; > olivier.matz@6wind.com > Subject: Re: [dpdk-dev] error in testpmd when CONFIG_RTE_BUILD_SHARED_LIB= =3Dy >=20 > > -----Original Message----- > > From: Bruce Richardson [mailto:bruce.richardson@intel.com] > > Sent: Wednesday, April 12, 2017 3:35 PM > > To: Shreyansh Jain > > Cc: Thomas Monjalon ; john miller > > ; dev@dpdk.org; olivier.matz@6wind.com > > Subject: Re: [dpdk-dev] error in testpmd when CONFIG_RTE_BUILD_SHARED_L= IB=3Dy > > > > On Wed, Apr 12, 2017 at 04:52:47AM +0000, Shreyansh Jain wrote: > > > > -----Original Message----- > > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > > Sent: Wednesday, April 12, 2017 12:58 AM > > > > To: john miller > > > > Cc: dev@dpdk.org; olivier.matz@6wind.com; Shreyansh Jain > > > > > > > > Subject: Re: [dpdk-dev] error in testpmd when > > CONFIG_RTE_BUILD_SHARED_LIB=3Dy > > > > > > > > 2017-04-11 14:02, john miller: > > > > > > > > > > We are seeing an issue when running from the head of the master b= ranch > > in > > > > dpdk-next-net and building with CONFIG_RTE_BUILD_SHARED_LIB=3Dy. = When we > > run > > > > testpmd using -d to point to our PMD we get this error > > > > > > > > > > EAL: Error - exiting with code: 1 > > > > > Cause: Creation of mbuf pool for socket 0 failed: Invalid argum= ent > > > > > > > > > > This error occurs as a result of the rte mempool ops table having= 0 > > > > entries. This table is populated from a call to > > rte_mempool_register_ops(). > > > > This function gets called in rte_mempool_ring.c via the static > > initialization > > > > MACRO MEMPOOL_REGISTER_OPS and exists in librte_mempool_ring.so. H= owever > > > > this library is not loaded when the rte_eal_init() gets called so t= he > > static > > > > initializers are not yet loaded. > > > > > > > > > > I am requesting advice on the proper way to repair this. > > > > > > "-d" the ring library (rte_mempool_ring) - just like any other shared= lib. > > > > > > > I think this is a bug that should be fixed. The user should not need to > > have to specify a mempool driver just to get testpmd working, so I thin= k > > the ring handler as default should be compiled in automatically so as t= o > > allow regular mempools to just work as before. >=20 > For Ring Mempool as default enabled, +1 Same thought here. Why just not have a default mempool driver always built in? Konstantin >=20 > > > > > This change was done recently to move ring handler into its separate > > drivers/mempool/ring directory. That also means it no longer is compile= d into > > the librte_mempool. > > > > > > > > > > > We should just add a better error message if no mempool driver is > > available. > > > > > > Yes, that is something to be improved. > > > > This should be fixed by always having a mempool driver installed. >=20 > Agree. > Otherwise also, the framework seems to be replying with a valid code 'EIN= VAL' for an invalid mempool specified. >=20 > > > > /Bruce