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 99E42A0A04 for ; Tue, 19 Jan 2021 04:45:36 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 82FBE140E11; Tue, 19 Jan 2021 04:45:36 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mails.dpdk.org (Postfix) with ESMTP id B9928140DE5; Tue, 19 Jan 2021 04:45:33 +0100 (CET) IronPort-SDR: +Z/uhXXF9oqpgxdYtCFLPrz9GU20ildcaTqnoI2+BOD/Cn6SXHpn/ErtNe4XMFKhYzk1GZd86O oafLSnlrPgfw== X-IronPort-AV: E=McAfee;i="6000,8403,9868"; a="165963783" X-IronPort-AV: E=Sophos;i="5.79,357,1602572400"; d="scan'208";a="165963783" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jan 2021 19:45:23 -0800 IronPort-SDR: raUud5L90+R7ORcrzsvnoL2oxN84n3edE1GqfnFhZbYmdOzyKfG0UbRgJlfpB9alQHxPbUke0J BSk46gFjUDdQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,357,1602572400"; d="scan'208";a="350374701" Received: from fmsmsx606.amr.corp.intel.com ([10.18.126.86]) by orsmga003.jf.intel.com with ESMTP; 18 Jan 2021 19:45:23 -0800 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by fmsmsx606.amr.corp.intel.com (10.18.126.86) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Mon, 18 Jan 2021 19:45:22 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX603.ccr.corp.intel.com (10.109.6.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 19 Jan 2021 11:45:20 +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.1713.004; Tue, 19 Jan 2021 11:45:20 +0800 From: "Zhang, Qi Z" To: "Ding, Xuan" , "Wu, Jingjing" , "Xing, Beilei" CC: "dev@dpdk.org" , "stable@dpdk.org" Thread-Topic: [PATCH v2] net/iavf: fix VIRTHCNL_OP_SET_RSS_HENA handling Thread-Index: AQHW7XW189uF90S/6UucEfrN+fXANaouTpBg Date: Tue, 19 Jan 2021 03:45:20 +0000 Message-ID: References: <20210118081506.107794-1-xuan.ding@intel.com> <20210118082826.1261-1-xuan.ding@intel.com> In-Reply-To: <20210118082826.1261-1-xuan.ding@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-stable] [PATCH v2] net/iavf: fix VIRTHCNL_OP_SET_RSS_HENA handling X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" > -----Original Message----- > From: Ding, Xuan > Sent: Monday, January 18, 2021 4:28 PM > To: Zhang, Qi Z ; Wu, Jingjing ; > Xing, Beilei > Cc: dev@dpdk.org; Ding, Xuan ; stable@dpdk.org > Subject: [PATCH v2] net/iavf: fix VIRTHCNL_OP_SET_RSS_HENA handling >=20 > Allow error to be returned for VIRTCHNL_OP_SET_RSS_HENA when set hena =3D= 0. > Add warning that PF does not support hena =3D 0 now. Actually this is not a fix, it's a workaround to handle some defect in lega= cy kernel driver. So changed title and commit log as below: Title: workaround RSS cleanup failure handling Allow to ignore error returned from virtual channel command VIRTCHNL_OP_SET_RSS_HENA with hena =3D 0 due to some legacy kernel driver does not support this. Add warning message when this happen. >=20 > Fixes: 95f2f0e9fc2a6("net/iavf: improve default RSS")=09 The fix line should be removed. > Cc: stable@dpdk.org >=20 > Signed-off-by: Xuan Ding Acked by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi