From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: davem@davemloft.net, netdev@vger.kernel.org,
oss-drivers@netronome.com,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH bpf-next 0/2] nfp: bpf: add programmable RSS support
Date: Tue, 8 May 2018 19:37:05 -0700 [thread overview]
Message-ID: <20180509023707.23601-1-jakub.kicinski@netronome.com> (raw)
Hi!
This small series adds a feature which extends BPF offload beyond
a pure host processing offload and firmly into the realm of
heterogeneous processing. Allowing offloaded XDP programs to set
the RX queue index opens the door for defining fully programmable
RSS/n-tuple filter replacement. In fact the device datapath will
skip the RSS processing completely if BPF decided on the queue
already, making the XDP program replace part of the standard NIC
datapath.
We hope some day the entire NIC datapath will be defined by BPF :)
Jakub Kicinski (2):
bpf: xdp: allow offloads to store into rx_queue_index
nfp: bpf: support setting the RX queue index
drivers/net/ethernet/netronome/nfp/bpf/fw.h | 1 +
drivers/net/ethernet/netronome/nfp/bpf/jit.c | 47 +++++++++++++++++++
drivers/net/ethernet/netronome/nfp/bpf/main.c | 11 +++++
drivers/net/ethernet/netronome/nfp/bpf/main.h | 8 ++++
.../net/ethernet/netronome/nfp/bpf/verifier.c | 28 ++++++++++-
drivers/net/ethernet/netronome/nfp/nfp_asm.h | 22 +++++----
include/linux/bpf.h | 2 +-
kernel/bpf/verifier.c | 2 +-
net/core/filter.c | 9 +++-
9 files changed, 115 insertions(+), 15 deletions(-)
--
2.17.0
next reply other threads:[~2018-05-09 2:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 2:37 Jakub Kicinski [this message]
2018-05-09 2:37 ` [PATCH bpf-next 1/2] bpf: xdp: allow offloads to store into rx_queue_index Jakub Kicinski
2018-05-09 2:37 ` [PATCH bpf-next 2/2] nfp: bpf: support setting the RX queue index Jakub Kicinski
2018-05-09 2:42 ` [PATCH bpf-next 0/2] nfp: bpf: add programmable RSS support Alexei Starovoitov
2018-05-09 16:09 ` Daniel Borkmann
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=20180509023707.23601-1-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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 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).