From: patchwork-bot+netdevbpf@kernel.org
To: Geliang Tang <geliang@kernel.org>
Cc: john.fastabend@gmail.com, jakub@cloudflare.com,
jiayuan.chen@linux.dev, edumazet@google.com,
ncardwell@google.com, kuniyu@google.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
matttbe@kernel.org, martineau@kernel.org, tanggeliang@kylinos.cn,
netdev@vger.kernel.org, bpf@vger.kernel.org,
mptcp@lists.linux.dev
Subject: Re: [PATCH bpf-next v4] bpf: drop duplicate check_app_limited in tcp_bpf_push
Date: Wed, 23 Sep 2026 02:10:08 +0000 [thread overview]
Message-ID: <179012940865.177114.1142007941387252817.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1f7dc605b16fc0590f7cbf5a27d57271926c01ce.1790074764.git.tanggeliang@kylinos.cn>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 22 Sep 2026 19:06:18 +0800 you wrote:
> From: Geliang Tang <tanggeliang@kylinos.cn>
>
> Commit c5c37af6ecad9 ("tcp: Convert do_tcp_sendpages() to use
> MSG_SPLICE_PAGES") moved tcp_rate_check_app_limited() inside
> do_tcp_sendpages(), turning it into a wrapper around tcp_sendmsg_locked().
> Later, commit ebf2e8860eea ("tcp_bpf: Inline do_tcp_sendpages as it's now
> a wrapper around tcp_sendmsg") inlined the wrapper in tcp_bpf_push() with
> direct tcp_sendmsg_locked() calls, which perform the check on every path
> that queues data, but kept the outer tcp_rate_check_app_limited() that
> was previously needed to cover do_tcp_sendpages(). The outer call is now
> redundant.
>
> [...]
Here is the summary with links:
- [bpf-next,v4] bpf: drop duplicate check_app_limited in tcp_bpf_push
https://git.kernel.org/bpf/bpf-next/c/91f8613d95ad
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:[~2026-09-23 2:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 11:06 [PATCH bpf-next v4] bpf: drop duplicate check_app_limited in tcp_bpf_push Geliang Tang
2026-09-22 11:57 ` bot+bpf-ci
2026-09-22 12:03 ` Jiayuan Chen
2026-09-23 2: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=179012940865.177114.1142007941387252817.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=geliang@kernel.org \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=martineau@kernel.org \
--cc=matttbe@kernel.org \
--cc=mptcp@lists.linux.dev \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tanggeliang@kylinos.cn \
/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