DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: dev@dpdk.org, Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH v4] ethdev: add isolated mode to flow API
Date: Wed, 14 Jun 2017 23:33:21 +0200	[thread overview]
Message-ID: <1756567.58yx1UZM0n@xps> (raw)
In-Reply-To: <df8c777e-9fc0-30c6-f670-662aa8bed96f@solarflare.com>

14/06/2017 17:41, Andrew Rybchenko:
> On 06/14/2017 05:48 PM, Adrien Mazarguil wrote:
> > Isolated mode can be requested by applications on individual ports to avoid
> > ingress traffic outside of the flow rules they define.
> >
> > Besides making ingress more deterministic, it allows PMDs to safely reuse
> > resources otherwise assigned to handle the remaining traffic, such as
> > global RSS configuration settings, VLAN filters, MAC address entries,
> > legacy filter API rules and so on in order to expand the set of possible
> > flow rule types.
> >
> > To minimize code complexity, PMDs implementing this mode may provide
> > partial (or even no) support for flow rules when not enabled (e.g. no
> > priorities, no RSS action). Applications written to use the flow API are
> > therefore encouraged to enable it.
> >
> > Once effective, leaving isolated mode may not be possible depending on PMD
> > implementation.
> >
> > Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
> > Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> > Cc: Andrew Rybchenko <arybchenko@solarflare.com>
> 
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>

Applied, thanks

      reply	other threads:[~2017-06-14 21:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 13:45 [dpdk-dev] [PATCH] " Adrien Mazarguil
2017-05-19  8:14 ` Adrien Mazarguil
2017-05-19 21:00   ` John Daley (johndale)
2017-05-22 10:17     ` Adrien Mazarguil
2017-05-24 13:53 ` Nélio Laranjeiro
2017-05-24 14:57 ` [dpdk-dev] [PATCH v2] " Adrien Mazarguil
2017-06-14 12:45   ` [dpdk-dev] [PATCH v3] " Adrien Mazarguil
2017-06-14 13:01     ` Andrew Rybchenko
2017-06-14 13:35       ` Adrien Mazarguil
2017-06-14 14:04         ` Andrew Rybchenko
2017-06-14 14:48     ` [dpdk-dev] [PATCH v4] " Adrien Mazarguil
2017-06-14 15:41       ` Andrew Rybchenko
2017-06-14 21:33         ` Thomas Monjalon [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=1756567.58yx1UZM0n@xps \
    --to=thomas@monjalon.net \
    --cc=adrien.mazarguil@6wind.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@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).