From: patchwork-bot+netdevbpf@kernel.org
To: Zijian Zhang <zijianzhang@bytedance.com>
Cc: bpf@vger.kernel.org, john.fastabend@gmail.com,
jakub@cloudflare.com, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, dsahern@kernel.org,
horms@kernel.org, ast@kernel.org, daniel@iogearbox.net,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 bpf 0/2] tcp_bpf: update the rmem scheduling for
Date: Fri, 20 Dec 2024 17:10:51 +0000 [thread overview]
Message-ID: <173471465149.2963436.10634845833925071160.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241210012039.1669389-1-zijianzhang@bytedance.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Tue, 10 Dec 2024 01:20:37 +0000 you wrote:
> From: Zijian Zhang <zijianzhang@bytedance.com>
>
> We should do sk_rmem_schedule instead of sk_wmem_schedule in function
> bpf_tcp_ingress. We also need to update sk_rmem_alloc in bpf_tcp_ingress
> accordingly to account for the rmem.
>
> v2:
> - Update the commit message to indicate the reason for msg->skb check
>
> [...]
Here is the summary with links:
- [v2,bpf,1/2] tcp_bpf: charge receive socket buffer in bpf_tcp_ingress()
https://git.kernel.org/bpf/bpf/c/54f89b3178d5
- [v2,bpf,2/2] tcp_bpf: add sk_rmem_alloc related logic for tcp_bpf ingress redirection
https://git.kernel.org/bpf/bpf/c/d888b7af7c14
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-12-20 17:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 1:20 [PATCH v2 bpf 0/2] tcp_bpf: update the rmem scheduling for zijianzhang
2024-12-10 1:20 ` [PATCH v2 bpf 1/2] tcp_bpf: charge receive socket buffer in bpf_tcp_ingress() zijianzhang
2024-12-10 1:20 ` [PATCH v2 bpf 2/2] tcp_bpf: add sk_rmem_alloc related logic for tcp_bpf ingress redirection zijianzhang
2024-12-20 16:51 ` [PATCH v2 bpf 0/2] tcp_bpf: update the rmem scheduling for John Fastabend
2024-12-20 17: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=173471465149.2963436.10634845833925071160.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=zijianzhang@bytedance.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