From: patchwork-bot+netdevbpf@kernel.org
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
cong.wang@bytedance.com, john.fastabend@gmail.com
Subject: Re: [PATCH RESEND bpf v3 0/8] sock_map: some bug fixes and improvements
Date: Mon, 21 Jun 2021 15:00:05 +0000 [thread overview]
Message-ID: <162428760509.31493.2198162085381420192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210615021342.7416-1-xiyou.wangcong@gmail.com>
Hello:
This series was applied to bpf/bpf.git (refs/heads/master):
On Mon, 14 Jun 2021 19:13:34 -0700 you wrote:
> From: Cong Wang <cong.wang@bytedance.com>
>
> This patchset contains a few bug fixes and improvements for sock_map.
>
> Patch 1 improves recvmsg() accuracy for UDP, patch 2 improves UDP
> non-blocking read() by retrying on EAGAIN. With both of them, the
> failure rate of the UDP test case goes down from 10% to 1%.
>
> [...]
Here is the summary with links:
- [RESEND,bpf,v3,1/8] skmsg: improve udp_bpf_recvmsg() accuracy
https://git.kernel.org/bpf/bpf/c/9f2470fbc4cb
- [RESEND,bpf,v3,2/8] selftests/bpf: Retry for EAGAIN in udp_redir_to_connected()
https://git.kernel.org/bpf/bpf/c/a7e65fe7d820
- [RESEND,bpf,v3,3/8] udp: fix a memory leak in udp_read_sock()
https://git.kernel.org/bpf/bpf/c/e00a5c331bf5
- [RESEND,bpf,v3,4/8] skmsg: clear skb redirect pointer before dropping it
https://git.kernel.org/bpf/bpf/c/30b9c54a707d
- [RESEND,bpf,v3,5/8] skmsg: fix a memory leak in sk_psock_verdict_apply()
https://git.kernel.org/bpf/bpf/c/0cf6672b23c8
- [RESEND,bpf,v3,6/8] skmsg: teach sk_psock_verdict_apply() to return errors
https://git.kernel.org/bpf/bpf/c/1581a6c1c329
- [RESEND,bpf,v3,7/8] skmsg: pass source psock to sk_psock_skb_redirect()
https://git.kernel.org/bpf/bpf/c/42830571f1fd
- [RESEND,bpf,v3,8/8] skmsg: increase sk->sk_drops when dropping packets
https://git.kernel.org/bpf/bpf/c/781dd0431eb5
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:[~2021-06-21 15:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 2:13 [PATCH RESEND bpf v3 0/8] sock_map: some bug fixes and improvements Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 1/8] skmsg: improve udp_bpf_recvmsg() accuracy Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 2/8] selftests/bpf: Retry for EAGAIN in udp_redir_to_connected() Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 3/8] udp: fix a memory leak in udp_read_sock() Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 4/8] skmsg: clear skb redirect pointer before dropping it Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 5/8] skmsg: fix a memory leak in sk_psock_verdict_apply() Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 6/8] skmsg: teach sk_psock_verdict_apply() to return errors Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 7/8] skmsg: pass source psock to sk_psock_skb_redirect() Cong Wang
2021-06-15 2:13 ` [PATCH RESEND bpf v3 8/8] skmsg: increase sk->sk_drops when dropping packets Cong Wang
2021-06-19 9:57 ` [PATCH RESEND bpf v3 0/8] sock_map: some bug fixes and improvements Jakub Sitnicki
2021-06-21 15:00 ` 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=162428760509.31493.2198162085381420192.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cong.wang@bytedance.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=xiyou.wangcong@gmail.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 NNTP newsgroup(s).