From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Walukiewicz, Miroslaw" Subject: Re: [PATCHv2 0/5] ethdev: add new API to retrieve RX/TX queue information Date: Thu, 18 Jun 2015 13:56:52 +0000 Message-ID: <7C4248CAE043B144B1CD242D27562653454ABDA5@IRSMSX104.ger.corp.intel.com> References: <1434560084-21237-2-git-send-email-konstantin.ananyev@intel.com> <1434633528-23329-1-git-send-email-konstantin.ananyev@intel.com> <7C4248CAE043B144B1CD242D27562653454ABD61@IRSMSX104.ger.corp.intel.com> <20150618133900.GD7972@bricha3-MOBL3> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Cc: "dev@dpdk.org" To: "Richardson, Bruce" Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id C9FF26849 for ; Thu, 18 Jun 2015 15:57:02 +0200 (CEST) In-Reply-To: <20150618133900.GD7972@bricha3-MOBL3> Content-Language: en-US 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" Yes, really I need a high performance function - it is especially useful on= TX path. Which queue query function are you talking here to be enhanced? Mirek > -----Original Message----- > From: Richardson, Bruce > Sent: Thursday, June 18, 2015 3:39 PM > To: Walukiewicz, Miroslaw > Cc: Ananyev, Konstantin; dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCHv2 0/5] ethdev: add new API to retrieve RX/= TX > queue information >=20 > On Thu, Jun 18, 2015 at 01:30:33PM +0000, Walukiewicz, Miroslaw wrote: > > Konstantin, > > > > Is there a possibility to read information about available space in NIC= queue > for TX. > > > > It is quite easy to compute (or even available directly) and very usef= ul > especially for application sending multi-descriptor packets like TCP TSO. > > > > Now there is no access to such information and the transmit packet func= tion > must be called to > > be sure that there is available space. > > > > Mirek > > >=20 > Hi Mirek, >=20 > I'm not sure this function is the right place for such a query. It seems = that > a function like you require needs to be used on the datapath, while this = API > is not planned to be high-performance. I think that it might be better to > add an equivalent function to the existing RX descriptor querying functio= n. >=20 > /Bruce >=20 > > > -----Original Message----- > > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Konstantin > Ananyev > > > Sent: Thursday, June 18, 2015 3:19 PM > > > To: dev@dpdk.org > > > Subject: [dpdk-dev] [PATCHv2 0/5] ethdev: add new API to retrieve RX/= TX > > > queue information > > > > > > Add the ability for the upper layer to query RX/TX queue information. > > > Right now supported for: > > > ixgbe, i40e, e1000 PMDs. > > > > > > Konstantin Ananyev (5): > > > ethdev: add new API to retrieve RX/TX queue information > > > i40e: add support for eth_(rxq|txq)_info_get > > > ixgbe: add support for eth_(rxq|txq)_info_get > > > e1000: add support for eth_(rxq|txq)_info_get > > > testpmd: add new command to display RX/TX queue information > > > > > > app/test-pmd/cmdline.c | 48 +++++++++++++++++++++++++ > > > app/test-pmd/config.c | 67 > > > ++++++++++++++++++++++++++++++++++ > > > app/test-pmd/testpmd.h | 2 ++ > > > drivers/net/e1000/e1000_ethdev.h | 12 +++++++ > > > drivers/net/e1000/em_ethdev.c | 2 ++ > > > drivers/net/e1000/em_rxtx.c | 38 ++++++++++++++++++++ > > > drivers/net/e1000/igb_ethdev.c | 4 +++ > > > drivers/net/e1000/igb_rxtx.c | 36 +++++++++++++++++++ > > > drivers/net/i40e/i40e_ethdev.c | 2 ++ > > > drivers/net/i40e/i40e_ethdev.h | 5 +++ > > > drivers/net/i40e/i40e_rxtx.c | 42 ++++++++++++++++++++++ > > > drivers/net/ixgbe/ixgbe_ethdev.c | 4 +++ > > > drivers/net/ixgbe/ixgbe_ethdev.h | 6 ++++ > > > drivers/net/ixgbe/ixgbe_rxtx.c | 42 ++++++++++++++++++++++ > > > lib/librte_ether/rte_ethdev.c | 54 ++++++++++++++++++++++++++++ > > > lib/librte_ether/rte_ethdev.h | 77 > > > +++++++++++++++++++++++++++++++++++++++- > > > 16 files changed, 440 insertions(+), 1 deletion(-) > > > > > > -- > > > 1.8.5.3 > >