From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
John McNamara <john.mcnamara@intel.com>,
"O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"Lu, Wenzhuo" <wenzhuo.lu@intel.com>,
John Daley <johndale@cisco.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Helin Zhang <helin.zhang@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Pascal Mazon <pascal.mazon@6wind.com>
Subject: Re: [PATCH] ethdev: add isolated mode to flow API
Date: Wed, 24 May 2017 15:53:33 +0200 [thread overview]
Message-ID: <20170524135333.GJ31330@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <4a269110b5623a0a72e4fe9d2636414de5921473.1492609343.git.adrien.mazarguil@6wind.com>
On Wed, Apr 19, 2017 at 03:45:31PM +0200, 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>
> Cc: Ferruh Yigit <ferruh.yigit@intel.com>
> Cc: John McNamara <john.mcnamara@intel.com>
> Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
> Cc: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
> Cc: John Daley <johndale@cisco.com>
> Cc: Konstantin Ananyev <konstantin.ananyev@intel.com>
> Cc: Helin Zhang <helin.zhang@intel.com>
> Cc: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> Cc: Andrew Rybchenko <arybchenko@solarflare.com>
> Cc: Pascal Mazon <pascal.mazon@6wind.com>
Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
By the way I have implemented it for mlx5 driver [1], your patch needs
to be updated on master-net, is does not apply like this.
Thanks,
[1] http://dpdk.org/dev/patchwork/patch/24487/
--
Nélio Laranjeiro
6WIND
next prev parent reply other threads:[~2017-05-24 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 13:45 [PATCH] ethdev: add isolated mode to flow API 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 [this message]
2017-05-24 14:57 ` [PATCH v2] " Adrien Mazarguil
2017-06-14 12:45 ` [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 ` [PATCH v4] " Adrien Mazarguil
2017-06-14 15:41 ` Andrew Rybchenko
2017-06-14 21:33 ` Thomas Monjalon
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=20170524135333.GJ31330@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=helin.zhang@intel.com \
--cc=john.mcnamara@intel.com \
--cc=johndale@cisco.com \
--cc=konstantin.ananyev@intel.com \
--cc=pascal.mazon@6wind.com \
--cc=thomas@monjalon.net \
--cc=tim.odriscoll@intel.com \
--cc=wenzhuo.lu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.