From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: alexei.starovoitov@gmail.com, daniel@iogearbox.net
Cc: netdev@vger.kernel.org, oss-drivers@netronome.com,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH bpf-next 0/3] nfp: bpf: support big map entries
Date: Mon, 1 Oct 2018 18:30:31 -0700 [thread overview]
Message-ID: <20181002013034.8144-1-jakub.kicinski@netronome.com> (raw)
Hi!
This series makes the control message parsing for interacting
with BPF maps more flexible. Up until now we had a hard limit
in the ABI for key and value size to be 64B at most. Using
TLV capability allows us to support large map entries.
Jakub Kicinski (3):
nfp: bpf: parse global BPF ABI version capability
nfp: allow apps to request larger MTU on control vNIC
nfp: bpf: allow control message sizing for map ops
drivers/net/ethernet/netronome/nfp/bpf/cmsg.c | 70 ++++++++++++++++---
drivers/net/ethernet/netronome/nfp/bpf/fw.h | 11 ++-
drivers/net/ethernet/netronome/nfp/bpf/main.c | 52 ++++++++++++--
drivers/net/ethernet/netronome/nfp/bpf/main.h | 11 +++
drivers/net/ethernet/netronome/nfp/nfp_app.h | 4 ++
.../ethernet/netronome/nfp/nfp_net_common.c | 14 +++-
.../net/ethernet/netronome/nfp/nfp_net_ctrl.h | 2 +-
7 files changed, 142 insertions(+), 22 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-02 8:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-02 1:30 Jakub Kicinski [this message]
2018-10-02 1:30 ` [PATCH bpf-next 1/3] nfp: bpf: parse global BPF ABI version capability Jakub Kicinski
2018-10-02 1:30 ` [PATCH bpf-next 2/3] nfp: allow apps to request larger MTU on control vNIC Jakub Kicinski
2018-10-02 1:30 ` [PATCH bpf-next 3/3] nfp: bpf: allow control message sizing for map ops Jakub Kicinski
2018-10-02 12:41 ` [PATCH bpf-next 0/3] nfp: bpf: support big map entries 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=20181002013034.8144-1-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.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