From: John Fastabend <john.fastabend@gmail.com>
To: jakub.kicinski@netronome.com, ast@kernel.org, daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: [bpf-next PATCH v3 0/2] bpftool support for sockmap use cases
Date: Mon, 15 Oct 2018 11:19:44 -0700 [thread overview]
Message-ID: <20181015181857.8673.46183.stgit@john-Precision-Tower-5810> (raw)
The first patch adds support for attaching programs to maps. This is
needed to support sock{map|hash} use from bpftool. Currently, I carry
around custom code to do this so doing it using standard bpftool will
be great.
The second patch adds a compat mode to ignore non-zero entries in
the map def. This allows using bpftool with maps that have a extra
fields that the user knows can be ignored. This is needed to work
correctly with maps being loaded by other tools or directly via
syscalls.
v3: add bash completion and doc updates for --mapcompat
---
John Fastabend (2):
bpf: bpftool, add support for attaching programs to maps
bpf: bpftool, add flag to allow non-compat map definitions
tools/bpf/bpftool/Documentation/bpftool-prog.rst | 11 ++
tools/bpf/bpftool/Documentation/bpftool.rst | 6 +
tools/bpf/bpftool/bash-completion/bpftool | 21 ++++-
tools/bpf/bpftool/main.c | 7 +-
tools/bpf/bpftool/main.h | 3 -
tools/bpf/bpftool/prog.c | 101 ++++++++++++++++++++++
6 files changed, 142 insertions(+), 7 deletions(-)
next reply other threads:[~2018-10-16 2:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 18:19 John Fastabend [this message]
2018-10-15 18:19 ` [bpf-next PATCH v3 1/2] bpf: bpftool, add support for attaching programs to maps John Fastabend
2018-10-15 18:19 ` [bpf-next PATCH v3 2/2] bpf: bpftool, add flag to allow non-compat map definitions John Fastabend
2018-10-15 18:26 ` Jakub Kicinski
2018-10-15 23:17 ` [bpf-next PATCH v3 0/2] bpftool support for sockmap use cases Alexei Starovoitov
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=20181015181857.8673.46183.stgit@john-Precision-Tower-5810 \
--to=john.fastabend@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.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