From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 40C06A0C50; Fri, 16 Jul 2021 10:15:23 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2AEB14067B; Fri, 16 Jul 2021 10:15:23 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id 2CD9D4067B; Fri, 16 Jul 2021 10:15:21 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10046"; a="208880116" X-IronPort-AV: E=Sophos;i="5.84,244,1620716400"; d="scan'208";a="208880116" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Jul 2021 01:15:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.84,244,1620716400"; d="scan'208";a="506393746" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by fmsmga002.fm.intel.com with ESMTP; 16 Jul 2021 01:15:20 -0700 Received: from shsmsx605.ccr.corp.intel.com (10.109.6.215) by fmsmsx603.amr.corp.intel.com (10.18.126.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Fri, 16 Jul 2021 01:15:19 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX605.ccr.corp.intel.com (10.109.6.215) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Fri, 16 Jul 2021 16:15:16 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.2242.010; Fri, 16 Jul 2021 16:15:16 +0800 From: "Zhang, Qi Z" To: "Xu, Ting" , "dev@dpdk.org" CC: "Wu, Jingjing" , "Xing, Beilei" , "stable@dpdk.org" Thread-Topic: [PATCH v2] net/iavf: fix wrong bandwidth unit in TM capability querying Thread-Index: AQHXeWTSA1t5JJ1a40eqZpesQz/x7KtFQnIw Date: Fri, 16 Jul 2021 08:15:16 +0000 Message-ID: References: <20210715020811.15577-1-ting.xu@intel.com> <20210715103606.13551-1-ting.xu@intel.com> In-Reply-To: <20210715103606.13551-1-ting.xu@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2] net/iavf: fix wrong bandwidth unit in TM capability querying X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Xu, Ting > Sent: Thursday, July 15, 2021 6:36 PM > To: dev@dpdk.org > Cc: Zhang, Qi Z ; Wu, Jingjing ; > Xing, Beilei ; Xu, Ting ; > stable@dpdk.org > Subject: [PATCH v2] net/iavf: fix wrong bandwidth unit in TM capability > querying >=20 > In IAVF node TM capability querying, the unit of bandwidth is Kbps, which= is > not correct according to TM specification. Change the unit to Byte per se= cond. > Refine some unclear comments as well. >=20 > Fixes: 44d0a720a538 ("net/iavf: query QoS capabilities and set queue TC > mapping") > Cc: stable@dpdk.org >=20 > Signed-off-by: Ting Xu Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi