From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2CC38A046B for ; Mon, 22 Jul 2019 08:06:47 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 788731B945; Mon, 22 Jul 2019 08:06:46 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id AB34B1B464 for ; Mon, 22 Jul 2019 08:06:45 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jul 2019 23:06:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,294,1559545200"; d="scan'208";a="188537431" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.110.185]) by fmsmga001.fm.intel.com with ESMTP; 21 Jul 2019 23:06:43 -0700 Date: Mon, 22 Jul 2019 20:48:09 +0800 From: Ye Xiaolong To: Hideyuki Yamashita Cc: "users@dpdk.org" Message-ID: <20190722124809.GC102705@intel.com> References: <20190719150846.9A1E.17218CA3@ntt-tx.co.jp_1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190719150846.9A1E.17218CA3@ntt-tx.co.jp_1> User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-users] Why flow can not be created? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi, On 07/19, Hideyuki Yamashita wrote: >Hello, > >I am trying to use rte_flow with i40e PMD. > >What I want to achieve is like following. > > ---(dst MAC=XorY && VID=AorB) ---> PHY --default(VID=B)--> Queue0 > VID=A && dstMAC=X----> Queue1 > VID=A && dstMAC=Y----> Queue2 > >I tried to create flow using testpmd, but failed. > >testpmd> flow create 0 ingress pattern eth dst is 11:22:33:44:55:66 type mask 0xffff / vlan tci is 150 / end quactions inqueue index 1 / end >Caught error type 13 (specific pattern item): cause: 0x17ff5e200, Invalid MAC_addr mask.3, : Invalid argument >testpmd> It failed due to the flow used in your example would use i40e fdir filter, and currently it doesn't support dst MAC. > >Note that I could create flow which matches with dst Mac address. >I could also create flow which matches with VID. If you create flow with dst MAC address only, then it's handled by ethertype filter which supports dst MAC. Thanks, Xiaolong > >---(dst MAC=XorYorZ) ---> PHY --default(Z)--> Queue0 > dstMAC=X----> Queue1 > dstMAC=Y----> Queue2 > >---(VID=AorB) ---> PHY --default(B)--> Queue0 > VID=A-------> Queue1 > >However when comined those two into one flow, testpmd failed to validate the flow. > > >Q1. Why above flow can not be created? >Q2. All the NICs supported by i40e-PMD do NOT provide above operation and packet classification features? >Q3. Are there any PMD/NIC which allow above operation? > > >Thaks in advance, > >Hideyuki Yamashita >NTT TechnoCross > >