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 175017D27 for ; Fri, 18 Aug 2017 20:05:21 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Aug 2017 11:05:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,393,1498546800"; d="scan'208";a="141957837" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by fmsmga006.fm.intel.com with ESMTP; 18 Aug 2017 11:05:20 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.220]) by IRSMSX109.ger.corp.intel.com ([169.254.13.76]) with mapi id 14.03.0319.002; Fri, 18 Aug 2017 19:05:19 +0100 From: "Dumitrescu, Cristian" To: Stephen Hemminger CC: Kevin Yan , "dev@dpdk.org" Thread-Topic: [dpdk-dev] DPDK qos support for 40G port Thread-Index: AdMMxKhWKp0eplWUQ4+rv61P+2CwUAAQjL5QAIvigwACN191kAAKjn4AAAOG9gA= Date: Fri, 18 Aug 2017 18:05:19 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA9C95D@IRSMSX108.ger.corp.intel.com> References: <3EB4FA525960D640B5BDFFD6A3D891267BA8A355@IRSMSX108.ger.corp.intel.com> <3EB4FA525960D640B5BDFFD6A3D891267BA9C525@IRSMSX108.ger.corp.intel.com> <20170818102158.1d5f7d0f@xeon-e3> In-Reply-To: <20170818102158.1d5f7d0f@xeon-e3> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] DPDK qos support for 40G port 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: Fri, 18 Aug 2017 18:05:22 -0000 > -----Original Message----- > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Friday, August 18, 2017 6:22 PM > To: Dumitrescu, Cristian > Cc: Kevin Yan ; dev@dpdk.org > Subject: Re: [dpdk-dev] DPDK qos support for 40G port >=20 > On Fri, 18 Aug 2017 11:24:12 +0000 > "Dumitrescu, Cristian" wrote: >=20 > > Hi Kevin, > > > > > Hi Cristian, > > > Sorry to bother again, could you give suggestions/hints of code chang= e to > > > support single 40G port? Because in our setup, we will use single 4= 0G > port > > > (Intel XL710) as the network interface. > > > > > > Or is there any workaround to bypass the limitation?(we are not willi= ng to > > > use 4*10G setup) > > > > > > Thanks. > > > > > > > Probably the easiest thing to do as workaround to support single port o= f > 40GbE rate is to change the code so that each credit is equivalent to 2 b= ytes > instead of one. This is likely to result in some scheduling accuracy loss= , but it > can be implemented relatively quickly while avoiding complex code changes= . > > > > Regards, > > Cristian > > >=20 > Maybe it is time to deprecate existing QoS since it has so many fixed lim= its > and start a new version which supports up to 400G and many more classes. >=20 > Something that integrated better with your new QoS framework. s/deprecate/improve I am working to push some updates to librte_meter library, librte_sched to = follow.