From: patchwork-bot+netdevbpf@kernel.org
To: Yixin Shen <bobankhshen@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@kernel.org, song@kernel.org,
yhs@fb.com
Subject: Re: [PATCH bpf-next v2 0/2] Allow BPF TCP CCs to write app_limited
Date: Wed, 29 Mar 2023 20:40:20 +0000 [thread overview]
Message-ID: <168012242022.23822.8467286004510025048.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230329073558.8136-1-bobankhshen@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 29 Mar 2023 07:35:56 +0000 you wrote:
> This series allow BPF TCP CCs to write app_limited of struct
> tcp_sock. A built-in CC or one from a kernel module is already
> able to write to app_limited of struct tcp_sock. Until now,
> a BPF CC doesn't have write access to this member of struct
> tcp_sock.
>
> v2:
> - Merge the test of writing app_limited into the test of
> writing sk_pacing. (Martin KaFai Lau)
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: allow a TCP CC to write app_limited
https://git.kernel.org/bpf/bpf-next/c/562dc56a8898
- [bpf-next,v2,2/2] selftests/bpf: test a BPF CC writing app_limited
https://git.kernel.org/bpf/bpf-next/c/4239561b69fe
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-29 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 7:35 [PATCH bpf-next v2 0/2] Allow BPF TCP CCs to write app_limited Yixin Shen
2023-03-29 7:35 ` [PATCH bpf-next v2 1/2] bpf: allow a TCP CC " Yixin Shen
2023-03-29 7:35 ` [PATCH bpf-next v2 2/2] selftests/bpf: test a BPF CC writing app_limited Yixin Shen
2023-03-29 20:40 ` 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=168012242022.23822.8467286004510025048.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bobankhshen@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=martin.lau@kernel.org \
--cc=song@kernel.org \
--cc=yhs@fb.com \
/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.