From: David Ahern <dsahern@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>, netdev@vger.kernel.org
Cc: Alexei Starovoitov <ast@fb.com>,
Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com
Subject: Re: [PATCH net-next 0/8] Introduce bpf ID
Date: Tue, 30 May 2017 18:35:37 -0600 [thread overview]
Message-ID: <19cd3d0a-12eb-b8ca-a054-62d86ba2a509@gmail.com> (raw)
In-Reply-To: <cover.1496189155.git.kafai@fb.com>
On 5/30/17 6:08 PM, Martin KaFai Lau wrote:
> This patch series:
> 1) Introduce ID for both bpf_prog and bpf_map.
> 2) Add bpf commands to iterate the prog IDs and map
> IDs of the system.
> 3) Add bpf commands to get a prog/map fd from an ID
> 4) Add bpf command to get prog/map info from a fd.
> The prog/map info is a jump start in this patchset
> and it is not meant to be a complete list. They can
> be extended in the future patches.
Interesting. This really simplifies the bpf retrieval I have been
working on:
https://github.com/dsahern/linux/commits/bpf/retrieve-bpf-wip
Having the net device, filter, route, socket, cgroup, etc return the ids
for attached programs solves the problem of getting a reference to all
of the places BPF programs can be placed.
This patch set turns an id into a fd, and my patches allow the fd to be
used to get the bpf code.
next prev parent reply other threads:[~2017-05-31 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 0:08 [PATCH net-next 0/8] Introduce bpf ID Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 1/8] bpf: Introduce bpf_prog ID Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 2/8] bpf: Introduce bpf_map ID Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 3/8] bpf: Add BPF_(PROG|MAP)_GET_NEXT_ID command Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 4/8] bpf: Add BPF_PROG_GET_FD_BY_ID Martin KaFai Lau
2017-05-31 3:21 ` kbuild test robot
2017-05-31 0:08 ` [PATCH net-next 5/8] bpf: Add BPF_MAP_GET_FD_BY_ID Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 6/8] bpf: Add jited_len to struct bpf_prog Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 7/8] bpf: Add BPF_OBJ_GET_INFO_BY_FD Martin KaFai Lau
2017-05-31 0:08 ` [PATCH net-next 8/8] bpf: Test for bpf ID Martin KaFai Lau
2017-05-31 0:35 ` David Ahern [this message]
2017-05-31 4:30 ` [PATCH net-next 0/8] Introduce " Martin KaFai Lau
2017-05-31 18:30 ` David Miller
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=19cd3d0a-12eb-b8ca-a054-62d86ba2a509@gmail.com \
--to=dsahern@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=kernel-team@fb.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;
as well as URLs for NNTP newsgroup(s).