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 07243A0C4B; Thu, 8 Jul 2021 07:28:46 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CD0734069C; Thu, 8 Jul 2021 07:28:45 +0200 (CEST) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 6C84940687 for ; Thu, 8 Jul 2021 07:28:44 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10038"; a="189125201" X-IronPort-AV: E=Sophos;i="5.84,222,1620716400"; d="scan'208";a="189125201" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Jul 2021 22:28:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.84,222,1620716400"; d="scan'208";a="648263745" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by fmsmga005.fm.intel.com with ESMTP; 07 Jul 2021 22:28:43 -0700 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) 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; Wed, 7 Jul 2021 22:28:42 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2242.10; Thu, 8 Jul 2021 13:28:41 +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; Thu, 8 Jul 2021 13:28:40 +0800 From: "Zhang, Qi Z" To: "Xu, Ting" , "dev@dpdk.org" CC: "Wu, Jingjing" , "Xing, Beilei" Thread-Topic: [PATCH v2] net/ice: support QoS BW config after VF reset in DCF Thread-Index: AQHXc6FE3G92hcLXcUKaJf7ZeJ/Zbqs4jNRw Date: Thu, 8 Jul 2021 05:28:40 +0000 Message-ID: References: <20210702150027.26294-1-ting.xu@intel.com> <20210708023346.34436-1-ting.xu@intel.com> In-Reply-To: <20210708023346.34436-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/ice: support QoS BW config after VF reset in DCF 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 8, 2021 10:34 AM > To: dev@dpdk.org > Cc: Zhang, Qi Z ; Wu, Jingjing ; > Xing, Beilei ; Xu, Ting > Subject: [PATCH v2] net/ice: support QoS BW config after VF reset in DCF >=20 > When VF reset happens, the QoS bandwidth configuration will be lost. If t= he > reset is not caused by DCB change, it is supposed to replay the bandwidth > configuration to VF by DCF. In this patch, when a vsi update PF event is > received from PF after VF reset, and it is confirmed that DCB is not chan= ged, > bandwidth configuration will be replayed. >=20 > Signed-off-by: Ting Xu Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi