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 414ACA0524; Tue, 13 Apr 2021 11:30:34 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 19DDC160D57; Tue, 13 Apr 2021 11:30:34 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id DCBA7160D46 for ; Tue, 13 Apr 2021 11:30:31 +0200 (CEST) IronPort-SDR: gpyF6+KyrE2O/8tWRoBix6ZlXKEVirnhltyyER5te8VbG79LGjz4S0KmZoVUUixmNT9WeLRAJ1 NQFJoH+8YjLw== X-IronPort-AV: E=McAfee;i="6200,9189,9952"; a="279680987" X-IronPort-AV: E=Sophos;i="5.82,219,1613462400"; d="scan'208";a="279680987" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Apr 2021 02:30:31 -0700 IronPort-SDR: KBTee33mLAj/yCV93IM/EgXwyVFWkDFOwii25q20LQEkKXC5+B6SV9c3W73RFsuDzHM3SY3If3 omTj0MManU0Q== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.82,219,1613462400"; d="scan'208";a="450331073" Received: from fmsmsx603.amr.corp.intel.com ([10.18.126.83]) by FMSMGA003.fm.intel.com with ESMTP; 13 Apr 2021 02:30:31 -0700 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) 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; Tue, 13 Apr 2021 02:30:30 -0700 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Tue, 13 Apr 2021 17:30:28 +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; Tue, 13 Apr 2021 17:30:27 +0800 From: "Zhang, Qi Z" To: "Guo, Jia" , "orika@nvidia.com" , "Xing, Beilei" , "Li, Xiaoyun" , "Wu, Jingjing" CC: "dev@dpdk.org" , "Xu, Ting" Thread-Topic: [PATCH v4 0/4] support flow for IP fragment in IAVF Thread-Index: AQHXMD0+4GWJ4rVCpkCPGmkOZh00z6qyLqAw Date: Tue, 13 Apr 2021 09:30:27 +0000 Message-ID: <7142ce04b0204fbf9bfa33604081194c@intel.com> References: <20210324134844.60410-1-jia.guo@intel.com> <20210413081032.60509-1-jia.guo@intel.com> In-Reply-To: <20210413081032.60509-1-jia.guo@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 v4 0/4] support flow for IP fragment in IAVF 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: Guo, Jia > Sent: Tuesday, April 13, 2021 4:10 PM > To: orika@nvidia.com; Zhang, Qi Z ; Xing, Beilei > ; Li, Xiaoyun ; Wu, Jingjing > > Cc: dev@dpdk.org; Xu, Ting ; Guo, Jia > Subject: [PATCH v4 0/4] support flow for IP fragment in IAVF >=20 > support flow for IP fragment in IAVF >=20 > v4: > add some part which should not be deleted > v3: > rebase code and fix some parsing issues > v2: > refine some input check >=20 > Jeff Guo (4): > app/testpmd: add packet id for IP fragment > common/iavf: add proto header for IP fragment > net/iavf: support RSS hash for IP fragment > net/iavf: support FDIR for IP fragment packet >=20 > app/test-pmd/cmdline_flow.c | 21 +- > drivers/common/iavf/virtchnl.h | 7 + > drivers/net/iavf/iavf_fdir.c | 386 ++++++++++++++++++--------- > drivers/net/iavf/iavf_generic_flow.c | 24 ++ > drivers/net/iavf/iavf_generic_flow.h | 8 + > drivers/net/iavf/iavf_hash.c | 83 +++++- > 6 files changed, 394 insertions(+), 135 deletions(-) >=20 > -- > 2.20.1 For Patch 2,3,4 Acked-by: Qi Zhang Applied to dpdk-next-net-intel. Thanks Qi