From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: alexei.starovoitov@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next] bpf: show in bpftool map overview whether btf is available
Date: Wed, 18 Jul 2018 11:08:36 -0700 [thread overview]
Message-ID: <20180718110836.3ff5f81a@cakuba.lan> (raw)
In-Reply-To: <20180718091942.2963-1-daniel@iogearbox.net>
On Wed, 18 Jul 2018 11:19:42 +0200, Daniel Borkmann wrote:
> For a quick overview in 'bpftool map' display 'btf' if it's
> available for the dump for a specific map:
>
> # bpftool map list
> 11: array flags 0x0 btf
> key 4B value 20B max_entries 40 memlock 4096B
>
> # bpftool --json --pretty map list
> [{
> "id": 11,
> "type": "array",
> "flags": 0,
> "btf_available": true,
> "bytes_key": 4,
> "bytes_value": 20,
> "max_entries": 40,
> "bytes_memlock": 4096
> }
> ]
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Hmm.. would it make sense to provide the actual BTF IDs instead of just
yes/no? At least in JSON?
next prev parent reply other threads:[~2018-07-18 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 9:19 [PATCH bpf-next] bpf: show in bpftool map overview whether btf is available Daniel Borkmann
2018-07-18 16:35 ` Martin KaFai Lau
2018-07-18 18:08 ` Jakub Kicinski [this message]
2018-07-19 15:45 ` 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=20180718110836.3ff5f81a@cakuba.lan \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--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