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 5A8EFA0A03; Tue, 19 Jan 2021 07:27:37 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CFDAF140D36; Tue, 19 Jan 2021 07:27:36 +0100 (CET) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by mails.dpdk.org (Postfix) with ESMTP id 20457140D35 for ; Tue, 19 Jan 2021 07:27:33 +0100 (CET) IronPort-SDR: ML4OqXCFjalvoq0JODQ+KSDPZoC0CcpRrmnBAjJ16U/DnqpN9dz/GI7gCsMorrzyUtarqEltd2 r9kAT4nZ+fkA== X-IronPort-AV: E=McAfee;i="6000,8403,9868"; a="197586309" X-IronPort-AV: E=Sophos;i="5.79,358,1602572400"; d="scan'208";a="197586309" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 18 Jan 2021 22:27:22 -0800 IronPort-SDR: oqxRyS7EECg/LpjsN+qoYCBXPJAUJt1q6Uuc51mc9LZSUlL8c+QpHF9wxW4hQ+7jwIbGhKea3e I6U6FKreuTQg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,358,1602572400"; d="scan'208";a="353704363" Received: from fmsmsx605.amr.corp.intel.com ([10.18.126.85]) by orsmga006.jf.intel.com with ESMTP; 18 Jan 2021 22:27:20 -0800 Received: from shsmsx605.ccr.corp.intel.com (10.109.6.215) by fmsmsx605.amr.corp.intel.com (10.18.126.85) 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 22:27:19 -0800 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.1713.5; Tue, 19 Jan 2021 14:27:18 +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 14:27:18 +0800 From: "Zhang, Qi Z" To: "Wang, Haiyue" , "dev@dpdk.org" CC: "Yang, Qiming" , "Fu, Qi" Thread-Topic: [PATCH v2] net/ice: refactor DCF VLAN handling Thread-Index: AQHW7ZCoLnUq8gVxXEGULgqCMQY+iaoufN1g Date: Tue, 19 Jan 2021 06:27:17 +0000 Message-ID: <9d5a2e8aa72b4184a75cd5ac701d4e7e@intel.com> References: <20210118082408.82713-1-haiyue.wang@intel.com> <20210118113830.83593-1-haiyue.wang@intel.com> In-Reply-To: <20210118113830.83593-1-haiyue.wang@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: refactor DCF VLAN handling 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: Wang, Haiyue > Sent: Monday, January 18, 2021 7:38 PM > To: dev@dpdk.org > Cc: Yang, Qiming ; Zhang, Qi Z ; > Fu, Qi ; Wang, Haiyue > Subject: [PATCH v2] net/ice: refactor DCF VLAN handling >=20 > Since DCF always configure the outer VLAN offloads for the target AVF, so > rename the related variables to align with this design. >=20 > Also, the DCF needs to trace the AVF reset status to re-apply the VLAN of= fload > setting, refactor the reset event handling to support this. >=20 > Change the VF representor API 'ethdev' parameter to 'vf_rep_eth_dev' to a= void > introducing confusion with VF representor eth_dev ops name. >=20 > Signed-off-by: Haiyue Wang Acked-by: Qi Zhang ] Applied to dpdk-next-net-intel. Thanks Qi