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 E1F2FA0548; Thu, 1 Apr 2021 14:10:57 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 62681141136; Thu, 1 Apr 2021 14:10:57 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by mails.dpdk.org (Postfix) with ESMTP id A76C5141133 for ; Thu, 1 Apr 2021 14:10:55 +0200 (CEST) IronPort-SDR: 1E5vsFAlRkIo9aH/Sn+902sjB/gJQIlRCUSJ71UOxO5ymSu1FYoVXFwIpxGmk6Zgn/ThEWYwET moTJ7f/ibgIw== X-IronPort-AV: E=McAfee;i="6000,8403,9940"; a="256214316" X-IronPort-AV: E=Sophos;i="5.81,296,1610438400"; d="scan'208";a="256214316" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Apr 2021 05:10:54 -0700 IronPort-SDR: osHLtb4/d1SLbIpNrq/VPqv1ZtxfO9ZkfX6OA1A9DEOA5Jl5+CxUGtYViU4/DjLyXDFORhPZj/ UbQXUZoDXfTg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.81,296,1610438400"; d="scan'208";a="446234100" Received: from fmsmsx602.amr.corp.intel.com ([10.18.126.82]) by fmsmga002.fm.intel.com with ESMTP; 01 Apr 2021 05:10:53 -0700 Received: from shsmsx606.ccr.corp.intel.com (10.109.6.216) by fmsmsx602.amr.corp.intel.com (10.18.126.82) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 1 Apr 2021 05:10:51 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX606.ccr.corp.intel.com (10.109.6.216) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 1 Apr 2021 20:10:49 +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; Thu, 1 Apr 2021 20:10:49 +0800 From: "Zhang, Qi Z" To: "Yan, Zhirun" , "dev@dpdk.org" , "Wang, Xiao W" CC: "Cao, Yahui" , "Guo, Junfeng" , "Xu, Ting" Thread-Topic: [PATCH v3] net/ice: support VXLAN VNI field in FDIR Thread-Index: AQHXJphNm2Kdxh2hCkCMVt3nnyDjq6qfksnw Date: Thu, 1 Apr 2021 12:10:49 +0000 Message-ID: <473c393a0d3242b48ec1ff3a769f5b7a@intel.com> References: <20210324082521.3862163-1-zhirun.yan@intel.com> <20210401013323.3186609-1-zhirun.yan@intel.com> In-Reply-To: <20210401013323.3186609-1-zhirun.yan@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 v3] net/ice: support VXLAN VNI field in FDIR 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: Yan, Zhirun > Sent: Thursday, April 1, 2021 9:33 AM > To: dev@dpdk.org; Zhang, Qi Z ; Wang, Xiao W > > Cc: Cao, Yahui ; Guo, Junfeng ; > Xu, Ting ; Yan, Zhirun > Subject: [PATCH v3] net/ice: support VXLAN VNI field in FDIR >=20 > Add support for VNI field in FDIR. Treat VXLAN flow type as > ICE_FLTR_PTYPE_NONF_IPV4_UDP_VXLAN to align with shared code. It allows > to match outer L2/L3, VNI and inner L2/L3 fields with VXLAN pattern. > VNI takes 24 bits in VXLAN header, but uses 32 bits for matching in share= d > code. The 8 bits reserved field adjacent should always be 0. >=20 > Signed-off-by: Zhirun Yan Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi