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 98D172C55 for ; Fri, 4 Aug 2017 11:57:15 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Aug 2017 02:57:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,320,1498546800"; d="scan'208";a="136117912" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by fmsmga006.fm.intel.com with ESMTP; 04 Aug 2017 02:57:13 -0700 Received: from irsmsx155.ger.corp.intel.com (163.33.192.3) by IRSMSX104.ger.corp.intel.com (163.33.3.159) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 4 Aug 2017 10:57:12 +0100 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.133]) by irsmsx155.ger.corp.intel.com ([169.254.14.182]) with mapi id 14.03.0319.002; Fri, 4 Aug 2017 10:57:12 +0100 From: "Dumitrescu, Cristian" To: Kevin Yan , "dev@dpdk.org" Thread-Topic: DPDK qos support for 40G port Thread-Index: AdMMxKhWKp0eplWUQ4+rv61P+2CwUAAQjL5Q Date: Fri, 4 Aug 2017 09:57:11 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA8A355@IRSMSX108.ger.corp.intel.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] 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, 04 Aug 2017 09:57:16 -0000 Hi Kevin, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Kevin Yan > Sent: Friday, August 4, 2017 2:55 AM > To: dev@dpdk.org > Subject: [dpdk-dev] DPDK qos support for 40G port >=20 > Hi, > I have a question about dpdk qos feature, in rte_sched.h= , ... > rate is type of uint32_t, but if physical port rate is 40= G bit/s, which is > 5G byte/s, 5G already exceed the max value of uint32_t, so I doult that 4= 0G is > not supported by dpdk qos lib, or any error of my understanding? >=20 Yes, your understanding is correct, currently the port rate in bytes per se= cond needs to be represented as 32-bit number. So, we can currently do single port with 10GbE and 25GbE rate, but not sing= le port of 40GbE or 100GbE. Please note that we can do 40GbE as 4 ports of = 10GbE each, which is a very common configuration for 40GbE. This limitation is not trivial to remove, i.e. more code is needed to remov= e this limitation than just changing the rate data type to uint64_t. Thanks for your feedback. Good to know that we should upgrade this library = to support 40GbE rates sooner rather than later. > Thanks and waiting for your reply! >=20 >=20 > BRs, > Kevin >=20 Regards, Cristian