From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
To: Ye Xiaolong <xiaolong.ye@intel.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Why flow can not be created?
Date: Tue, 23 Jul 2019 15:26:37 +0900 [thread overview]
Message-ID: <20190723152636.9A24.17218CA3@ntt-tx.co.jp_1> (raw)
In-Reply-To: <20190722124809.GC102705@intel.com>
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
> >
> >
next prev parent reply other threads:[~2019-07-23 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 6:08 Hideyuki Yamashita
2019-07-22 12:48 ` Ye Xiaolong
2019-07-23 6:26 ` Hideyuki Yamashita [this message]
2019-07-30 10:37 ` Hideyuki Yamashita
2019-07-30 12:25 ` Adrien Mazarguil
2019-07-31 2:30 ` Hideyuki Yamashita
2019-08-02 6:06 ` Hideyuki Yamashita
2019-08-06 9:12 ` Adrien Mazarguil
2019-08-06 9:59 ` Moti Haimovsky
2019-08-09 6:05 ` Hideyuki Yamashita
2019-08-14 5:56 ` [dpdk-users] How L2 broadcast is handled under rte_flow? Hideyuki Yamashita
2019-08-29 3:11 ` Hideyuki Yamashita
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190723152636.9A24.17218CA3@ntt-tx.co.jp_1 \
--to=yamashita.hideyuki@ntt-tx.co.jp \
--cc=users@dpdk.org \
--cc=xiaolong.ye@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).