From: Eric Dumazet <eric.dumazet@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
David Miller <davem@davemloft.net>,
kernel-team@fb.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next 00/13] Introduce BPF STRUCT_OPS
Date: Fri, 13 Dec 2019 18:26:18 -0800 [thread overview]
Message-ID: <3928131b-2c70-759a-c12b-e7258942e189@gmail.com> (raw)
In-Reply-To: <20191214004737.1652076-1-kafai@fb.com>
On 12/13/19 4:47 PM, Martin KaFai Lau wrote:
> This series introduces BPF STRUCT_OPS. It is an infra to allow
> implementing some specific kernel's function pointers in BPF.
> The first use case included in this series is to implement
> TCP congestion control algorithm in BPF (i.e. implement
> struct tcp_congestion_ops in BPF).
>
> There has been attempt to move the TCP CC to the user space
> (e.g. CCP in TCP). The common arguments are faster turn around,
> get away from long-tail kernel versions in production...etc,
> which are legit points.
>
> BPF has been the continuous effort to join both kernel and
> userspace upsides together (e.g. XDP to gain the performance
> advantage without bypassing the kernel). The recent BPF
> advancements (in particular BTF-aware verifier, BPF trampoline,
> BPF CO-RE...) made implementing kernel struct ops (e.g. tcp cc)
> possible in BPF.
>
> The idea is to allow implementing tcp_congestion_ops in bpf.
> It allows a faster turnaround for testing algorithm in the
> production while leveraging the existing (and continue growing) BPF
> feature/framework instead of building one specifically for
> userspace TCP CC.
>
This is awesome work Martin !
prev parent reply other threads:[~2019-12-14 2:26 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-14 0:47 [PATCH bpf-next 00/13] Introduce BPF STRUCT_OPS Martin KaFai Lau
2019-12-14 0:47 ` [PATCH bpf-next 01/13] bpf: Save PTR_TO_BTF_ID register state when spilling to stack Martin KaFai Lau
2019-12-16 19:48 ` Yonghong Song
2019-12-14 0:47 ` [PATCH bpf-next 02/13] bpf: Avoid storing modifier to info->btf_id Martin KaFai Lau
2019-12-16 21:34 ` Yonghong Song
2019-12-14 0:47 ` [PATCH bpf-next 03/13] bpf: Add enum support to btf_ctx_access() Martin KaFai Lau
2019-12-16 21:36 ` Yonghong Song
2019-12-14 0:47 ` [PATCH bpf-next 04/13] bpf: Support bitfield read access in btf_struct_access Martin KaFai Lau
2019-12-16 22:05 ` Yonghong Song
2019-12-14 0:47 ` [PATCH bpf-next 05/13] bpf: Introduce BPF_PROG_TYPE_STRUCT_OPS Martin KaFai Lau
2019-12-17 6:14 ` Yonghong Song
2019-12-18 16:41 ` Martin Lau
2019-12-14 0:47 ` [PATCH bpf-next 06/13] bpf: Introduce BPF_MAP_TYPE_STRUCT_OPS Martin KaFai Lau
2019-12-17 7:48 ` [Potential Spoof] " Yonghong Song
2019-12-20 7:22 ` Martin Lau
2019-12-20 16:52 ` Martin Lau
2019-12-20 18:41 ` Andrii Nakryiko
2019-12-14 0:47 ` [PATCH bpf-next 07/13] bpf: tcp: Support tcp_congestion_ops in bpf Martin KaFai Lau
2019-12-17 17:36 ` Yonghong Song
2019-12-14 0:47 ` [PATCH bpf-next 08/13] bpf: Add BPF_FUNC_tcp_send_ack helper Martin KaFai Lau
2019-12-17 17:41 ` Yonghong Song
2019-12-14 0:47 ` [PATCH bpf-next 09/13] bpf: Add BPF_FUNC_jiffies Martin KaFai Lau
2019-12-14 1:59 ` Eric Dumazet
2019-12-14 19:25 ` Neal Cardwell
2019-12-16 19:30 ` Martin Lau
2019-12-17 8:26 ` Jakub Sitnicki
2019-12-17 18:22 ` Martin Lau
2019-12-17 21:04 ` Eric Dumazet
2019-12-18 9:03 ` Jakub Sitnicki
2019-12-16 19:14 ` Martin Lau
2019-12-16 19:33 ` Eric Dumazet
2019-12-16 21:17 ` Martin Lau
2019-12-16 23:08 ` Alexei Starovoitov
2019-12-17 0:34 ` Eric Dumazet
2019-12-14 0:48 ` [PATCH bpf-next 10/13] bpf: Synch uapi bpf.h to tools/ Martin KaFai Lau
2019-12-14 0:48 ` [PATCH bpf-next 11/13] bpf: libbpf: Add STRUCT_OPS support Martin KaFai Lau
2019-12-18 3:07 ` Andrii Nakryiko
2019-12-18 7:03 ` Martin Lau
2019-12-18 7:20 ` Martin Lau
2019-12-18 16:36 ` Andrii Nakryiko
2019-12-18 16:34 ` Andrii Nakryiko
2019-12-18 17:33 ` Martin Lau
2019-12-18 18:14 ` Andrii Nakryiko
2019-12-18 20:19 ` Martin Lau
2019-12-19 8:53 ` Toke Høiland-Jørgensen
2019-12-19 20:49 ` Andrii Nakryiko
2019-12-20 10:16 ` Toke Høiland-Jørgensen
2019-12-20 17:34 ` Andrii Nakryiko
2019-12-14 0:48 ` [PATCH bpf-next 12/13] bpf: Add bpf_dctcp example Martin KaFai Lau
2019-12-14 0:48 ` [PATCH bpf-next 13/13] bpf: Add bpf_cubic example Martin KaFai Lau
2019-12-14 2:26 ` Eric Dumazet [this message]
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=3928131b-2c70-759a-c12b-e7258942e189@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.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).