DPDK usage discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Antoine POLLENUS <a.pollenus@deltacast.tv>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] [rte_flow]How to redirect all non matching traffic to a specific queue
Date: Mon, 29 Jul 2019 16:44:27 +0200	[thread overview]
Message-ID: <20190729144427.GZ4512@6wind.com> (raw)
In-Reply-To: <20190717151714.779770aa@xps13>

On Wed, Jul 17, 2019 at 03:17:14PM -0700, Stephen Hemminger wrote:
> On Wed, 17 Jul 2019 11:46:17 +0000
> Antoine POLLENUS <a.pollenus@deltacast.tv> wrote:
> 
> > Hello,
> > 
> > I have a problem in my DPDK implementation,
> > 
> > I'm redirecting/filtering ingress traffic to a specific queue depending on the udp port using rte_flow.
> > 
> > Now that I have that I would like to redirect all non-matching packets to a specific queue.
> > 
> > How can I do that with RTE_FLOW ?
> > 
> > Thank you in advance for your answer.
> > 
> > Regards,
> > 
> > Antoine Pollenus
> 
> rte_flow supports INVERT as a pattern match. That is what you want.
> Not all hardware supports it.

Just checked, unfortunately no driver supports this pattern item at the
moment.

Assuming the intent is to dedicate a queue or a set of queues to matching
traffic and a different set to leftover traffic *without* overlap between
the two, you can rely on priorities as a workaround:

- Rule with priority 0: match specific UDP ports and redirect that to a
  specific queue (QUEUE action) or a group of queues (RSS action).

- Rule with priority 1: match everything (i.e. empty pattern) and spread
  that into the remaining queues (QUEUE or RSS action depending on the
  number of target queues).

-- 
Adrien Mazarguil
6WIND

      reply	other threads:[~2019-07-29 14:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-17 11:46 Antoine POLLENUS
2019-07-17 22:17 ` Stephen Hemminger
2019-07-29 14:44   ` Adrien Mazarguil [this message]

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=20190729144427.GZ4512@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=a.pollenus@deltacast.tv \
    --cc=stephen@networkplumber.org \
    --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).