From: Jakub Kicinski <kubakici@wp•pl>
To: Edward Cree <ecree@solarflare•com>
Cc: <linux-net-drivers@solarflare•com>,
David Miller <davem@davemloft•net>,
netdev <netdev@vger•kernel.org>,
"John W. Linville" <linville@tuxdriver•com>,
Or Gerlitz <gerlitz.or@gmail•com>,
Alexander Duyck <alexander.h.duyck@intel•com>
Subject: Re: [PATCH RESEND net-next 0/2] ntuple filters with RSS
Date: Tue, 27 Feb 2018 15:47:57 -0800 [thread overview]
Message-ID: <20180227154757.4e5f334a@cakuba.netronome.com> (raw)
In-Reply-To: <85718e87-e999-abb7-4a84-84858ee86a8e@solarflare.com>
On Tue, 27 Feb 2018 17:59:12 +0000, Edward Cree wrote:
> This series introduces the ability to mark an ethtool steering filter to use
> RSS spreading, and the ability to create and configure multiple RSS contexts
> with different indirection tables, hash keys, and hash fields.
> An implementation for the sfc driver (for 7000-series and later SFC NICs) is
> included in patch 2/2.
>
> The anticipated use case of this feature is for steering traffic destined for
> a container (or virtual machine) to the subset of CPUs on which processes in
> the container (or the VM's vCPUs) are bound, while retaining the scalability
> of RSS spreading from the viewpoint inside the container.
> The use of both a base queue number (ring_cookie) and indirection table is
> intended to allow re-use of a single RSS context to target multiple sets of
> CPUs. For instance, if an 8-core system is hosting three containers on CPUs
> [1,2], [3,4] and [6,7], then a single RSS context with an equal-weight [0,1]
> indirection table could be used to target all three containers by setting
> ring_cookie to 1, 3 and 6 on the respective filters.
Please, let's stop extending ethtool_rx_flow APIs. I bit my tongue
when Intel was adding their "redirection to VF" based on ethtool ntuples
and look now they're adding the same functionality with flower :| And
wonder how to handle two interfaces doing the same thing.
On the use case itself, I wonder how much sense that makes. Can your
hardware not tag the packet as well so you could then mux it to
something like macvlan offload?
CC: Alex, Or
next prev parent reply other threads:[~2018-02-27 23:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 17:59 [PATCH RESEND net-next 0/2] ntuple filters with RSS Edward Cree
2018-02-27 18:02 ` [PATCH net-next 1/2] net: ethtool: extend RXNFC API to support RSS spreading of filter matches Edward Cree
2018-02-27 18:03 ` [PATCH net-next 2/2] sfc: support RSS spreading of ethtool ntuple filters Edward Cree
2018-03-01 20:51 ` kbuild test robot
2018-02-27 23:47 ` Jakub Kicinski [this message]
2018-02-28 1:24 ` [PATCH RESEND net-next 0/2] ntuple filters with RSS Alexander Duyck
2018-03-02 15:24 ` Edward Cree
2018-03-02 18:55 ` Jakub Kicinski
2018-03-02 23:24 ` Alexander Duyck
2018-03-01 18:36 ` David Miller
2018-03-02 16:01 ` Edward Cree
2018-03-02 17:49 ` David Riddoch
2018-03-07 15:24 ` David Miller
2018-03-07 15:40 ` Edward Cree
2018-03-07 20:55 ` David Miller
[not found] <533b5eff-49b6-16c3-9873-dda3fb05c3d4@solarflare.com>
2018-02-27 17:38 ` David Miller
2018-02-27 17:55 ` Edward Cree
2018-02-27 19:28 ` John W. Linville
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=20180227154757.4e5f334a@cakuba.netronome.com \
--to=kubakici@wp$(echo .)pl \
--cc=alexander.h.duyck@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ecree@solarflare$(echo .)com \
--cc=gerlitz.or@gmail$(echo .)com \
--cc=linux-net-drivers@solarflare$(echo .)com \
--cc=linville@tuxdriver$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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