From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 71F845926 for ; Fri, 1 Aug 2014 19:37:17 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 01 Aug 2014 10:39:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.01,781,1400050800"; d="scan'208";a="570554293" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by fmsmga001.fm.intel.com with ESMTP; 01 Aug 2014 10:38:48 -0700 Received: from irsmsx152.ger.corp.intel.com (163.33.192.66) by IRSMSX103.ger.corp.intel.com (163.33.3.157) with Microsoft SMTP Server (TLS) id 14.3.195.1; Fri, 1 Aug 2014 18:38:47 +0100 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.131]) by IRSMSX152.ger.corp.intel.com ([169.254.6.214]) with mapi id 14.03.0195.001; Fri, 1 Aug 2014 18:38:47 +0100 From: "Richardson, Bruce" To: Sunil Bojanapally , "Liu, Jijiang" Thread-Topic: [dpdk-dev] VMDq + DCB: 128 Tx queues Thread-Index: AQHPrUddqMtakK4jNECsyWx0uKK0dZu7TKUAgACO2ICAAChlgA== Date: Fri, 1 Aug 2014 17:38:46 +0000 Message-ID: <59AF69C657FD0841A61C55336867B5B0343D47C5@IRSMSX103.ger.corp.intel.com> References: <53DB21E4.1030405@ericsson.com>, <1ED644BD7E0A5F4091CF203DAFB8E4CC01D5618F@SHSMSX101.ccr.corp.intel.com> <2093D5E48464CB43A02B12483F758F7A1A3BB243@ESESSMB105.ericsson.se> In-Reply-To: <2093D5E48464CB43A02B12483F758F7A1A3BB243@ESESSMB105.ericsson.se> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] VMDq + DCB: 128 Tx queues 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: Fri, 01 Aug 2014 17:37:18 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sunil Bojanapally > Sent: Friday, August 01, 2014 9:13 AM > To: Liu, Jijiang > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] VMDq + DCB: 128 Tx queues >=20 > Thanks Liu for the pointer to function implemented in testpmd.c >=20 > Just want to know in RX configured pools, what scheduling method is used = in > polling the queues. How the queues are polled when in vmdq+dcb mode is entirely up to the appli= cation, as the queue id passed into the rx_burst function will refer direct= ly to one of the hardware queues to be read. There is no behind-the-scenes = magic and prioritization of packets being done, the app knows best what way= it wants the packets to be read and processed. Regards, /Bruce >=20 > -Sunil >=20 > On Fri, Aug 01, 2014 at 1:11 PM, Liu, Jijiang > > wrote: >=20 >=20 > Yes, if you hope TX is configured DCB mode, and 128 TX queues are needed.= In > testpmd codes, there is an example how to use 128 RX queue and 128 TX que= ue > simultaneously in vmdq+dcb mode. > The example function is get_eth_dcb_conf() in testpmd.c file. >=20 > BRs, > Jijiang Liu >=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Sunil Bojanapally > Sent: Friday, August 01, 2014 1:13 PM > To: dev@dpdk.org > Subject: [dpdk-dev] VMDq + DCB: 128 Tx queues >=20 > Hi team, >=20 > As per dpdk programming guide on VMDq+DCB will configure each Ethernet po= rt > to 16 pools with 8 queues each. Which means per port will have 128 Rx & T= x > queues. >=20 > The question is, in order to have end 2 end QoS support the port should g= et > configured with 128 Rx as well as 128 Tx queues ? >=20 > Note: I am considering same port for Rx & Tx. >=20 > Thanks, > Sunil