From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 709E47CEA for ; Fri, 18 Aug 2017 13:24:15 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Aug 2017 04:24:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,392,1498546800"; d="scan'208";a="301767082" Received: from irsmsx105.ger.corp.intel.com ([163.33.3.28]) by fmsmga004.fm.intel.com with ESMTP; 18 Aug 2017 04:24:13 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.220]) by irsmsx105.ger.corp.intel.com ([169.254.7.25]) with mapi id 14.03.0319.002; Fri, 18 Aug 2017 12:24:12 +0100 From: "Dumitrescu, Cristian" To: Kevin Yan , "dev@dpdk.org" Thread-Topic: DPDK qos support for 40G port Thread-Index: AdMMxKhWKp0eplWUQ4+rv61P+2CwUAAQjL5QAIvigwACN191kA== Date: Fri, 18 Aug 2017 11:24:12 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BA9C525@IRSMSX108.ger.corp.intel.com> References: <3EB4FA525960D640B5BDFFD6A3D891267BA8A355@IRSMSX108.ger.corp.intel.com> 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.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 11:24:15 -0000 Hi Kevin, > Hi Cristian, > Sorry to bother again, could you give suggestions/hints of code change to > support single 40G port? Because in our setup, we will use single 40G p= ort > (Intel XL710) as the network interface. >=20 > Or is there any workaround to bypass the limitation?(we are not willing t= o > use 4*10G setup) >=20 > Thanks. >=20 Probably the easiest thing to do as workaround to support single port of 40= GbE rate is to change the code so that each credit is equivalent to 2 bytes= instead of one. This is likely to result in some scheduling accuracy loss,= but it can be implemented relatively quickly while avoiding complex code c= hanges. Regards, Cristian