From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Cc: Ye Xiaolong <xiaolong.ye@intel.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Why flow can not be created?
Date: Tue, 30 Jul 2019 14:25:39 +0200 [thread overview]
Message-ID: <20190730122539.GD4512@6wind.com> (raw)
In-Reply-To: <20190730193738.8EBB.17218CA3@ntt-tx.co.jp_1>
On Tue, Jul 30, 2019 at 07:37:38PM +0900, Hideyuki Yamashita wrote:
> 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.
Unfortunately right now trial & error using testpmd is the most effective
approach to determine whether specific combinations are supported by any
given NIC.
Ideally doc/guides/nics/features.rst [1] should document each rte_flow
feature reflected in doc/guide/nics/features/*.ini for individual PMDs [2],
but that list is currently too incomplete to be useful.
Now to answer your question, although those are likely not the only ones, I
know from experience that both mlx4 and mlx5 support flow rules matching VID
+ dst MAC simultaneously.
[1] http://doc.dpdk.org/guides/nics/features.html
[2] http://doc.dpdk.org/guides/nics/overview.html
--
Adrien Mazarguil
6WIND
next prev parent reply other threads:[~2019-07-30 12:25 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
2019-07-30 10:37 ` Hideyuki Yamashita
2019-07-30 12:25 ` Adrien Mazarguil [this message]
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=20190730122539.GD4512@6wind.com \
--to=adrien.mazarguil@6wind.com \
--cc=users@dpdk.org \
--cc=xiaolong.ye@intel.com \
--cc=yamashita.hideyuki@ntt-tx.co.jp \
/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).