[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190320142346.3b552895@cakuba.netronome.com>
Date: Wed, 20 Mar 2019 14:23:46 -0700
From: Jakub Kicinski <jakub.kicinski@...ronome.com>
To: Alban Crequy <alban.crequy@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, alban@...volk.io, iago@...volk.io
Subject: Re: [PATCH bpf-next v1 4/7] tools: bpftool: implement map exec
command
On Wed, 20 Mar 2019 18:33:29 +0100, Alban Crequy wrote:
> From: Alban Crequy <alban@...volk.io>
>
> The map exec commands allows to open an existing map and pass the file
> descriptor to a child process. This enables applications to use an
> existing BPF map even when they don't support bpffs.
>
> Example of usage:
> # bpftool map exec pinned /sys/fs/bpf/foo fd 99 cmd -- readlink /proc/self/fd/99
> anon_inode:bpf-map
Would you mind telling us a little more about the use for this feature?
It seems fairly limited. If it's about probing objects (finding out if
they are a map or a program) perhaps we can add a command just for that?
(I guess bpftool -f isn't really the cleanest way of getting at that
info.)
> Documentation and bash completion updated as well.
>
> Signed-off-by: Alban Crequy <alban@...volk.io>
Powered by blists - more mailing lists