From: Yonghong Song <yhs@fb•com>
To: <ast@fb•com>, <daniel@iogearbox•net>, <netdev@vger•kernel.org>
Cc: <kernel-team@fb•com>
Subject: [PATCH bpf-next 0/2] bpf: add bpffs/bpftool dump for prog_array and map_in_map maps
Date: Thu, 6 Sep 2018 17:26:03 -0700 [thread overview]
Message-ID: <20180907002605.1408960-1-yhs@fb.com> (raw)
The support to dump program array and map_in_map maps
for bpffs and bpftool is added. Patch #1 added bpffs support
and Patch #2 added bpftool support. Please see
individual patches for example output.
Yonghong Song (2):
bpf: add bpffs pretty print for program array map
tools/bpf: bpftool: support prog array map and map of maps
kernel/bpf/arraymap.c | 25 ++++++++++++++++++++++++-
tools/bpf/bpftool/map.c | 11 +++--------
2 files changed, 27 insertions(+), 9 deletions(-)
--
2.17.1
next reply other threads:[~2018-09-07 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 0:26 Yonghong Song [this message]
2018-09-07 0:26 ` [PATCH bpf-next 1/2] bpf: add bpffs pretty print for program array map Yonghong Song
2018-09-07 0:26 ` [PATCH bpf-next 2/2] tools/bpf: bpftool: support prog array map and map of maps Yonghong Song
2018-09-11 21:20 ` [PATCH bpf-next 0/2] bpf: add bpffs/bpftool dump for prog_array and map_in_map maps 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=20180907002605.1408960-1-yhs@fb.com \
--to=yhs@fb$(echo .)com \
--cc=ast@fb$(echo .)com \
--cc=daniel@iogearbox$(echo .)net \
--cc=kernel-team@fb$(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