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 4AEEBA0546; Fri, 30 Apr 2021 16:07:11 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B49644014F; Fri, 30 Apr 2021 16:07:10 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id 92AF54013F for ; Fri, 30 Apr 2021 16:07:09 +0200 (CEST) IronPort-SDR: DjXVl2xOluU60H9nwgpxpKNG93WE43+4Gh0yNgNATnu95Hvx2bM4NjLnMK/h0MJiRN9Ii7HZmF hvD8p3ID5pLg== X-IronPort-AV: E=McAfee;i="6200,9189,9970"; a="197379138" X-IronPort-AV: E=Sophos;i="5.82,262,1613462400"; d="scan'208";a="197379138" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 30 Apr 2021 07:07:08 -0700 IronPort-SDR: +3ibti9kET50T4GaVSgTaD5uY/yegFofLMvWdQKZA+b1Ds1imjx6AySFjjSCWe2VhKSgHdbJvL uwPJXh8++Nzw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.82,262,1613462400"; d="scan'208";a="387371546" Received: from fmsmsx604.amr.corp.intel.com ([10.18.126.84]) by orsmga003.jf.intel.com with ESMTP; 30 Apr 2021 07:07:08 -0700 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) by fmsmsx604.amr.corp.intel.com (10.18.126.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Fri, 30 Apr 2021 07:07:07 -0700 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.2106.2; Fri, 30 Apr 2021 22:07:05 +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.2106.013; Fri, 30 Apr 2021 22:07:05 +0800 From: "Zhang, Qi Z" To: "Sun, QinX" , "Rong, Leyi" , "Lu, Wenzhuo" CC: "dev@dpdk.org" , "Rong, Leyi" Thread-Topic: [dpdk-dev] [PATCH] net/iavf: fix VLAN tag extraction handling in AVX512 path Thread-Index: AQHXNyWn/J2gCJkDjkeMJHMbR5RLbqrKkfOAgAKT4qA= Date: Fri, 30 Apr 2021 14:07:04 +0000 Message-ID: <71d63932c0bb43a481f8072518fc52ff@intel.com> References: <20210422024830.10617-1-leyi.rong@intel.com> In-Reply-To: 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] net/iavf: fix VLAN tag extraction handling in AVX512 path 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: Sun, QinX > Sent: Thursday, April 29, 2021 2:45 PM > To: Rong, Leyi ; Zhang, Qi Z ;= Lu, > Wenzhuo > Cc: dev@dpdk.org; Rong, Leyi > Subject: RE: [dpdk-dev] [PATCH] net/iavf: fix VLAN tag extraction handlin= g in > AVX512 path >=20 > > -----Original Message----- > > From: dev On Behalf Of Leyi Rong > > Sent: Thursday, April 22, 2021 10:49 AM > > To: Zhang, Qi Z ; Lu, Wenzhuo > > > > Cc: dev@dpdk.org; Rong, Leyi > > Subject: [dpdk-dev] [PATCH] net/iavf: fix VLAN tag extraction handling > > in > > AVX512 path > > > > The new VIRTCHNL_VF_OFFLOAD_VLAN_V2 capability added support that > > allows the PF to set the location of the RX VLAN tag for stripping offl= oads. > > > > So the VF needs to extract the VLAN tag according to the location flags= . > > > > This patch is the fix for AVX512 path, as AVX2 is already fixed. > > > > Fixes: 9c9aa0040344 ("net/iavf: add offload path for Rx AVX512 flex > > descriptor") > > > > Signed-off-by: Leyi Rong >=20 > Tested-by: Qin Sun Applied to dpdk-next-net-intel. Thanks Qi