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 1AB3AA0A0E; Thu, 4 Feb 2021 09:12:36 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9755A2405BE; Thu, 4 Feb 2021 09:12:35 +0100 (CET) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id E324424059E for ; Thu, 4 Feb 2021 09:12:33 +0100 (CET) IronPort-SDR: F3+TWDRTixZ07twyBVEqRhxaSezCwOWlFRMgIeEGwxAqVeXV8Bean6z5SF57wHjO0XG8Pk/geZ 7dYj2sUtGgEg== X-IronPort-AV: E=McAfee;i="6000,8403,9884"; a="168875692" X-IronPort-AV: E=Sophos;i="5.79,400,1602572400"; d="scan'208";a="168875692" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Feb 2021 00:12:32 -0800 IronPort-SDR: DvnrN/JdFUVqiROfFZlUKWGy4oLUHxqgVKJD4WhiaRjVwvR+tJzGwPUwWhH7uJiykqbIIWWC8c nVjXpjQZJgcQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,400,1602572400"; d="scan'208";a="372862374" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by orsmga002.jf.intel.com with ESMTP; 04 Feb 2021 00:12:32 -0800 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) 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.2106.2; Thu, 4 Feb 2021 00:12:31 -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; Thu, 4 Feb 2021 16:12:29 +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; Thu, 4 Feb 2021 16:12:29 +0800 From: "Zhang, Qi Z" To: "Xing, Beilei" , "Li, Xiaoyun" , "Wu, Jingjing" , "dev@dpdk.org" Thread-Topic: [PATCH] net/iavf: fix VLAN insert issue Thread-Index: AQHW+sMh+lzsdUiHoUa1wKRuah1qKqpHpWAw Date: Thu, 4 Feb 2021 08:12:29 +0000 Message-ID: <56be2e46574d4e2e9489daff260418c9@intel.com> References: <20210204031118.603270-1-xiaoyun.li@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 insert issue 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: dev On Behalf Of Xing, Beilei > Sent: Thursday, February 4, 2021 2:58 PM > To: Li, Xiaoyun ; Wu, Jingjing ; > dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] net/iavf: fix VLAN insert issue >=20 >=20 >=20 > > -----Original Message----- > > From: Li, Xiaoyun > > Sent: Thursday, February 4, 2021 11:11 AM > > To: Wu, Jingjing ; Xing, Beilei > > ; dev@dpdk.org > > Cc: Li, Xiaoyun > > Subject: [PATCH] net/iavf: fix VLAN insert issue > > > > The new VIRTCHNL_VF_OFFLOAD_VLAN_V2 capability allows PF to set the > > location of TX VLAN insertion. > > > > So VF needs to insert VLAN tag according to the location flags. > > > > Fixes: 1c301e8c3cff ("net/iavf: support new VLAN capabilities") > > > > Signed-off-by: Xiaoyun Li >=20 > Acked-by: Beilei Xing Applied to dpdk-next-net-intel. Thanks Qi