From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,MAILING_LIST_MULTI, PDS_BAD_THREAD_QP_64,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65B5CC11F67 for ; Wed, 30 Jun 2021 02:00:13 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id B4FD961D62 for ; Wed, 30 Jun 2021 02:00:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B4FD961D62 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BFBDA41109; Wed, 30 Jun 2021 04:00:10 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by mails.dpdk.org (Postfix) with ESMTP id 466F140E01; Wed, 30 Jun 2021 04:00:08 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10030"; a="208220972" X-IronPort-AV: E=Sophos;i="5.83,310,1616482800"; d="scan'208";a="208220972" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jun 2021 19:00:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.83,310,1616482800"; d="scan'208";a="425680227" Received: from fmsmsx605.amr.corp.intel.com ([10.18.126.85]) by orsmga002.jf.intel.com with ESMTP; 29 Jun 2021 19:00:05 -0700 Received: from shsmsx603.ccr.corp.intel.com (10.109.6.143) 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.2242.4; Tue, 29 Jun 2021 19:00:05 -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.2242.4; Wed, 30 Jun 2021 10:00:03 +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.2242.008; Wed, 30 Jun 2021 10:00:03 +0800 From: "Zhang, Qi Z" To: "Chen, LingliX" , "Xing, Beilei" CC: "dev@dpdk.org" , "Xing, Beilei" , "stable@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v2] net/i40e: fix FDIR input set conflict issue Thread-Index: AQHXaMyI/gdFjiQUfkaJcGCif/WrOKsiYJcAgAl1AlA= Date: Wed, 30 Jun 2021 02:00:03 +0000 Message-ID: References: <20210624070759.45204-1-beilei.xing@intel.com> <20210624072956.45489-1-beilei.xing@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 v2] net/i40e: fix FDIR input set conflict 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: Chen, LingliX > Sent: Thursday, June 24, 2021 5:35 PM > To: Xing, Beilei ; Zhang, Qi Z > Cc: dev@dpdk.org; Xing, Beilei ; stable@dpdk.org > Subject: RE: [dpdk-dev] [PATCH v2] net/i40e: fix FDIR input set conflict = issue >=20 >=20 > > -----Original Message----- > > From: dev On Behalf Of beilei.xing@intel.com > > Sent: Thursday, June 24, 2021 3:30 PM > > To: Zhang, Qi Z > > Cc: dev@dpdk.org; Xing, Beilei ; stable@dpdk.org > > Subject: [dpdk-dev] [PATCH v2] net/i40e: fix FDIR input set conflict is= sue > > > > From: Beilei Xing > > > > Currently, there'll be conflict error when running the following comman= ds: > > 1. flow create 0 ingress > > pattern eth / ipv4 / udp src is 32 / end > > actions queue index 2 / end > > 2. flow destroy 0 rule 0 > > 3. flow create 0 ingress > > pattern eth / ipv4 / udp dst is 32 / end > > actions queue index 2 / end > > > > This patch fixes the input set conflict issue. > > > > Fixes: 42044b69c67d ("net/i40e: support input set selection for FDIR") > > Fixes: 4a072ad43442 ("net/i40e: fix flow director config after flow val= idate") > > Cc: stable@dpdk.org > > > > Signed-off-by: Beilei Xing >=20 > Tested-by: Lingli Chen Applied to dpdk-next-net-intel. Thanks Qi