From: patchwork-bot+netdevbpf@kernel.org
To: Kui-Feng Lee <kuifeng@meta.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, martin.lau@linux.dev,
song@kernel.org, kernel-team@meta.com, andrii@kernel.org,
sdf@google.com
Subject: Re: [PATCH bpf-next v12 0/8] Transit between BPF TCP congestion controls.
Date: Thu, 23 Mar 2023 06:10:20 +0000 [thread overview]
Message-ID: <167955182049.23814.16375855529117553677.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230323032405.3735486-1-kuifeng@meta.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 22 Mar 2023 20:23:57 -0700 you wrote:
> Major changes:
>
> - Create bpf_links in the kernel for BPF struct_ops to register and
> unregister it.
>
> - Enables switching between implementations of bpf-tcp-cc under a
> name instantly by replacing the backing struct_ops map of a
> bpf_link.
>
> [...]
Here is the summary with links:
- [bpf-next,v12,1/8] bpf: Retire the struct_ops map kvalue->refcnt.
https://git.kernel.org/bpf/bpf-next/c/b671c2067a04
- [bpf-next,v12,2/8] net: Update an existing TCP congestion control algorithm.
https://git.kernel.org/bpf/bpf-next/c/8fb1a76a0f35
- [bpf-next,v12,3/8] bpf: Create links for BPF struct_ops maps.
https://git.kernel.org/bpf/bpf-next/c/68b04864ca42
- [bpf-next,v12,4/8] libbpf: Create a bpf_link in bpf_map__attach_struct_ops().
https://git.kernel.org/bpf/bpf-next/c/8d1608d70927
- [bpf-next,v12,5/8] bpf: Update the struct_ops of a bpf_link.
https://git.kernel.org/bpf/bpf-next/c/aef56f2e918b
- [bpf-next,v12,6/8] libbpf: Update a bpf_link with another struct_ops.
https://git.kernel.org/bpf/bpf-next/c/912dd4b0c2a5
- [bpf-next,v12,7/8] libbpf: Use .struct_ops.link section to indicate a struct_ops with a link.
https://git.kernel.org/bpf/bpf-next/c/809a69d61899
- [bpf-next,v12,8/8] selftests/bpf: Test switching TCP Congestion Control algorithms.
https://git.kernel.org/bpf/bpf-next/c/06da9f3bd641
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-23 6:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 3:23 [PATCH bpf-next v12 0/8] Transit between BPF TCP congestion controls Kui-Feng Lee
2023-03-23 3:23 ` [PATCH bpf-next v12 1/8] bpf: Retire the struct_ops map kvalue->refcnt Kui-Feng Lee
2023-03-23 3:23 ` [PATCH bpf-next v12 2/8] net: Update an existing TCP congestion control algorithm Kui-Feng Lee
2023-03-23 3:24 ` [PATCH bpf-next v12 3/8] bpf: Create links for BPF struct_ops maps Kui-Feng Lee
2023-03-23 3:24 ` [PATCH bpf-next v12 4/8] libbpf: Create a bpf_link in bpf_map__attach_struct_ops() Kui-Feng Lee
2023-03-23 3:24 ` [PATCH bpf-next v12 5/8] bpf: Update the struct_ops of a bpf_link Kui-Feng Lee
2023-03-23 3:24 ` [PATCH bpf-next v12 6/8] libbpf: Update a bpf_link with another struct_ops Kui-Feng Lee
2023-03-23 3:24 ` [PATCH bpf-next v12 7/8] libbpf: Use .struct_ops.link section to indicate a struct_ops with a link Kui-Feng Lee
2023-03-23 3:24 ` [PATCH bpf-next v12 8/8] selftests/bpf: Test switching TCP Congestion Control algorithms Kui-Feng Lee
2023-03-23 6:05 ` Martin KaFai Lau
2023-03-23 14:50 ` Kui-Feng Lee
2023-03-23 6:10 ` patchwork-bot+netdevbpf [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=167955182049.23814.16375855529117553677.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.