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 7D448A0613 for ; Tue, 30 Jul 2019 12:38:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BDCA91C043; Tue, 30 Jul 2019 12:38:00 +0200 (CEST) Received: from dish-sg.nttdocomo.co.jp (dish-sg.nttdocomo.co.jp [202.19.227.74]) by dpdk.org (Postfix) with ESMTP id 297451C038 for ; Tue, 30 Jul 2019 12:37:58 +0200 (CEST) X-dD-Source: Outbound Received: from zssg-mailmd104.ddreams.local (zssg-mailmd900.ddreams.local [10.160.172.63]) by zssg-mailou104.ddreams.local (Postfix) with ESMTP id B09D3120118; Tue, 30 Jul 2019 19:37:55 +0900 (JST) Received: from t131sg-mailcc11.ddreams.local (t131sg-mailcc11.ddreams.local [100.66.31.86]) by zssg-mailmd104.ddreams.local (dDREAMS) with ESMTP id <0PVG0099DAV75P50@dDREAMS>; Tue, 30 Jul 2019 19:37:55 +0900 (JST) Received: from t131sg-mailcc12 (localhost [127.0.0.1]) by t131sg-mailcc11.ddreams.local (unknown) with SMTP id x6UAbtwm014422; Tue, 30 Jul 2019 19:37:55 +0900 Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by zssg-mailmf106.ddreams.local (Postfix) with ESMTP id D59487E603B; Tue, 30 Jul 2019 19:37:39 +0900 (JST) Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id D43CD8E6061; Tue, 30 Jul 2019 19:37:39 +0900 (JST) Received: from localhost (unknown [127.0.0.1]) by IMSVA (Postfix) with SMTP id D2E238E605A; Tue, 30 Jul 2019 19:37:39 +0900 (JST) X-IMSS-HAND-OFF-DIRECTIVE: localhost:10026 Received: from zssg-mailmf106.ddreams.local (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 149EE8E6042; Tue, 30 Jul 2019 19:37:39 +0900 (JST) Received: from zssg-mailua106.ddreams.local (unknown [10.160.172.62]) by zssg-mailmf106.ddreams.local (Postfix) with ESMTP; Tue, 30 Jul 2019 19:37:39 +0900 (JST) Received: from [10.87.198.18] (unknown [10.160.183.129]) by zssg-mailua106.ddreams.local (dDREAMS) with ESMTPA id <0PVG00FTUAUQFDD0@dDREAMS>; Tue, 30 Jul 2019 19:37:38 +0900 (JST) Date: Tue, 30 Jul 2019 19:37:38 +0900 From: Hideyuki Yamashita In-reply-to: <20190723152636.9A24.17218CA3@ntt-tx.co.jp_1> References: <20190722124809.GC102705@intel.com> <20190723152636.9A24.17218CA3@ntt-tx.co.jp_1> Message-id: <20190730193738.8EBB.17218CA3@ntt-tx.co.jp_1> MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Mailer: Becky! ver. 2.74.02 [ja] X-TM-AS-GCONF: 00 To: Hideyuki Yamashita Cc: Ye Xiaolong , "users@dpdk.org" 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" Hello, Does anybody whether PMD other than i40e support VID+dstMAC matching? It is very hard for me to read all PMD code for just to know the support of VID+dstMAC as matching pattern. Somebody, please help me. BR, HIdeyuki Yamashita NTT TechnoCross > Hello Ye, > > Thanks for your quick reponse. > Please see inline tagged with [Hideyuki] > > > 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. > [Hideyuki] > Are there any special reason why dst MAC is NOT supported by > i40e_flow_parse_fdir_filter()? > > Maybe this is related to the following my original question. > > >Q2. All the NICs supported by i40e-PMD do NOT provide above operation and packet classification features? > > > > > > > >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. > [Hideyuki] > Yes, I confirmed it. > > Are there any way to achieve my goal by combining two flows > (one for dst MAC and other for VID)? > > > Also it is appreciated if you or someone can provide answer > for my question below. > > >Q3. Are there any PMD/NIC which allow above operation? > > Thanks! > > BR, > Hideyuki Yamashita > NTT TechnoCross > > > > 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 > > > > > > > >