From: patchwork-bot+netdevbpf@kernel.org
To: Miao Xu <miaxu@meta.com>
Cc: edumazet@google.com, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, kafai@meta.com,
netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/3] Add new args into tcp_congestion_ops' cong_control
Date: Thu, 02 May 2024 23:40:30 +0000 [thread overview]
Message-ID: <171469323022.18467.15980884788609184083.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240502042318.801932-1-miaxu@meta.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Wed, 1 May 2024 21:23:15 -0700 you wrote:
> This patchset attempts to add two new arguments into the hookpoint
> cong_control in tcp_congestion_ops. The new arguments are inherited
> from the caller tcp_cong_control and can be used by any bpf cc prog
> that implements its own logic inside this hookpoint.
>
> Please review. Thanks a lot!
>
> [...]
Here is the summary with links:
- [net-next,v3,1/3] tcp: Add new args for cong_control in tcp_congestion_ops
https://git.kernel.org/bpf/bpf-next/c/57bfc7605ca5
- [net-next,v3,2/3] bpf: tcp: Allow to write tp->snd_cwnd_stamp in bpf_tcp_ca
https://git.kernel.org/bpf/bpf-next/c/0325cbd21e3c
- [net-next,v3,3/3] selftests/bpf: Add test for the use of new args in cong_control
https://git.kernel.org/bpf/bpf-next/c/96c3490d6423
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:[~2024-05-02 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 4:23 [PATCH net-next v3 0/3] Add new args into tcp_congestion_ops' cong_control Miao Xu
2024-05-02 4:23 ` [PATCH net-next v3 1/3] tcp: Add new args for cong_control in tcp_congestion_ops Miao Xu
2024-05-02 4:23 ` [PATCH net-next v3 2/3] bpf: tcp: Allow to write tp->snd_cwnd_stamp in bpf_tcp_ca Miao Xu
2024-05-02 4:23 ` [PATCH net-next v3 3/3] selftests/bpf: Add test for the use of new args in cong_control Miao Xu
2024-05-02 23:39 ` Martin KaFai Lau
2024-05-02 23: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=171469323022.18467.15980884788609184083.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kafai@meta.com \
--cc=kuba@kernel.org \
--cc=miaxu@meta.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).