From: David Ahern <dsahern@gmail.com>
To: Alexei Starovoitov <ast@fb.com>, Jakub Kicinski <kubakici@wp.pl>,
Martin KaFai Lau <kafai@fb.com>,
Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
kernel-team@fb.com
Subject: Re: [PATCH v2 net-next 0/8] Introduce bpf ID
Date: Thu, 1 Jun 2017 11:51:24 -0600 [thread overview]
Message-ID: <18d3c571-7434-eaea-43dc-d237712309d1@gmail.com> (raw)
In-Reply-To: <6ab73989-6246-ba15-7178-7863a110165c@fb.com>
On 6/1/17 11:24 AM, Alexei Starovoitov wrote:
>
> what problem are we trying to solve?
> If we don't agree on the problem, we won't be able to agree on the
> solution.
I want the ability to retrieve the BPF instructions pushed to the
kernel. Not just for cgroups and VRF, but everywhere - cgroups, sockets,
xdp, filters, etc. I have this stated many times, including to you at
netconf in April. From that discussion and the discussion on the RFC
patch I sent in February, I thought we had an agreement that saving the
instructions was the first step.
Quentin at 6wind has expressed a similar interest for cls_bpf and
act_bpf code.
I read Jakub's email as wanting the same but for XDP.
The patches I referenced earlier save the original instructions and
enable them to be read by userspace from an fd return by the bpf
syscall. Combine that with the ID and we have a solution.
next prev parent reply other threads:[~2017-06-01 17:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 18:58 [PATCH v2 net-next 0/8] Introduce bpf ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 1/8] bpf: Introduce bpf_prog ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 2/8] bpf: Introduce bpf_map ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 3/8] bpf: Add BPF_(PROG|MAP)_GET_NEXT_ID command Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 4/8] bpf: Add BPF_PROG_GET_FD_BY_ID Martin KaFai Lau
2017-05-31 18:58 ` [PATCH v2 net-next 5/8] bpf: Add BPF_MAP_GET_FD_BY_ID Martin KaFai Lau
2017-05-31 18:59 ` [PATCH v2 net-next 6/8] bpf: Add jited_len to struct bpf_prog Martin KaFai Lau
2017-05-31 18:59 ` [PATCH v2 net-next 7/8] bpf: Add BPF_OBJ_GET_INFO_BY_FD Martin KaFai Lau
2017-05-31 18:59 ` [PATCH v2 net-next 8/8] bpf: Test for bpf ID Martin KaFai Lau
2017-05-31 23:35 ` [PATCH v2 net-next 0/8] Introduce " David Miller
2017-06-03 1:08 ` Martin KaFai Lau
2017-06-01 2:22 ` Jakub Kicinski
2017-06-01 13:55 ` David Ahern
2017-06-01 17:24 ` Alexei Starovoitov
2017-06-01 17:51 ` David Ahern [this message]
2017-06-01 18:27 ` Alexei Starovoitov
2017-06-01 18:33 ` David Miller
2017-06-01 18:57 ` Jakub Kicinski
2017-06-01 18:52 ` David Ahern
2017-06-01 18:56 ` David Miller
2017-06-01 19:00 ` Jakub Kicinski
2017-06-01 21:48 ` Alexei Starovoitov
2017-06-02 11:39 ` David Ahern
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=18d3c571-7434-eaea-43dc-d237712309d1@gmail.com \
--to=dsahern@gmail.com \
--cc=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=hannes@stressinduktion.org \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=kubakici@wp.pl \
--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).