From: Stephen Hemminger <stephen@networkplumber.org>
To: Huai-En Tseng <the@csie.io>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] direct specific packets to specific receive queue
Date: Wed, 3 Jul 2019 07:51:10 -0700 [thread overview]
Message-ID: <20190703075110.13d496ee@hermes.lan> (raw)
In-Reply-To: <3D036938-873A-44AC-B42F-B63909ADAFF1@csie.io>
On Wed, 3 Jul 2019 16:05:34 +0800
Huai-En Tseng <the@csie.io> wrote:
> Hi,
>
> I suppose below three things to understand what difference between flex filter, fdir, flex payload and how to use them by tracing source code in testpmd.
>
> First, while I use flex filter API with rte_eth_dev_filter_ctrl(), RTE_ETH_FILTER_FLEXIBLE and struct rte_eth_flex_filter on my CX4 and X520 its not working.
>
> And I find that in dpdk NIC driver there are only a little NICs like igb NIC support it, so I assume flex filter does not support most NICs such as i40e, ixgbe, ixgbevf and mlx5.
>
> Second, I assume the fdir API is a smaller set which is included the flex filter API.
>
> Third, flex payload is kind of flex filter API application.
>
> Is all my assumption right?
>
> And is there any full support hardware list?
>
> Last question, is there any method that I can direct specific packets to specific receive queue?
>
> I want to direct pppoe packets to specific receive queue.
>
> I have tried the raw fdir API but it has limited function in X520, and testpmd flex filter is not working on my CX4 and X520 too.
>
> I also find there is a feature DDP in Intel 700 series NICs but it seems only detects pppoe header but I need to detect ppp header in pppoe header.
>
> Thanks a lot.
Did you know that flex filter and fdir are older API's that were only supported on a few Intel NIC's.
Use rte_flow instead.
next prev parent reply other threads:[~2019-07-03 14:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 8:05 Huai-En Tseng
2019-07-03 14:51 ` Stephen Hemminger [this message]
2019-07-04 3:54 ` Huai-En Tseng
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=20190703075110.13d496ee@hermes.lan \
--to=stephen@networkplumber.org \
--cc=the@csie.io \
--cc=users@dpdk.org \
/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).