From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 44177C2FA for ; Wed, 17 Feb 2016 18:36:59 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP; 17 Feb 2016 09:36:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,461,1449561600"; d="scan'208";a="654340342" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.208.63]) by FMSMGA003.fm.intel.com with SMTP; 17 Feb 2016 09:36:56 -0800 Received: by (sSMTP sendmail emulation); Wed, 17 Feb 2016 17:36:55 +0025 Date: Wed, 17 Feb 2016 17:36:55 +0000 From: Bruce Richardson To: Ferruh Yigit Message-ID: <20160217173655.GD11736@bricha3-MOBL3> References: <1454087782-15085-1-git-send-email-ferruh.yigit@intel.com> <1454087782-15085-3-git-send-email-ferruh.yigit@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1454087782-15085-3-git-send-email-ferruh.yigit@intel.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org, =?iso-8859-1?Q?Nicol=E1s?= Pernas Maradei Subject: Re: [dpdk-dev] [PATCH 2/3] ring: remove duplicate fields in internal data struct 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: Wed, 17 Feb 2016 17:36:59 -0000 On Fri, Jan 29, 2016 at 05:16:21PM +0000, Ferruh Yigit wrote: > 1- Remove duplicate nb_rx/tx_queues fields from internals > 2- Remove data->rx/tx_queues allocation, whose auto allocated by > libether > 3- Remove duplicate data->rx/tx_queues[i] assignments > > Signed-off-by: Ferruh Yigit > --- > drivers/net/ring/rte_eth_ring.c | 52 +++++++++++------------------------------ > 1 file changed, 14 insertions(+), 38 deletions(-) > Hi Ferruh, does this patch not break rte_eth_from_ring() and rte_eth_from_rings() since the "auto allocation" you refer to is only performed on eth_dev_configure, I believe. Currently, you can create an rte_ring and then use it as though it were an ethdev by calling: port_id = rte_eth_from_ring(r) With this change, I believe the user instead has to now call eth_from_ring, then do a series of configure and queue setup calls just to make the new ethdev usable. Regards. /Bruce