From: patchwork-bot+netdevbpf@kernel•org
To: John Fastabend <john.fastabend@gmail•com>
Cc: jakub@cloudflare•com, ast@kernel•org, daniel@iogearbox•net,
bpf@vger•kernel.org, netdev@vger•kernel.org
Subject: Re: [bpf PATCH v3 0/6] sockmap fixes
Date: Tue, 17 Nov 2020 23:20:05 +0000 [thread overview]
Message-ID: <160565520577.16897.8462803955194787332.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <160556562395.73229.12161576665124541961.stgit@john-XPS-13-9370>
Hello:
This series was applied to bpf/bpf.git (refs/heads/master):
On Mon, 16 Nov 2020 14:27:23 -0800 you wrote:
> This includes fixes for sockmap found after I started running skmsg and
> verdict programs on systems that I use daily. To date with attached
> series I've been running for multiple weeks without seeing any issues
> on systems doing calls, mail, movies, etc.
>
> Also I started running packetdrill and after this series last remaining
> fix needed is to handle MSG_EOR correctly. This will come as a follow
> up to this, but because we use sendpage to pass pages into TCP stack
> we need to enable TCP side some.
>
> [...]
Here is the summary with links:
- [bpf,v3,1/6] bpf, sockmap: fix partial copy_page_to_iter so progress can still be made
https://git.kernel.org/bpf/bpf/c/c9c89dcd872e
- [bpf,v3,2/6] bpf, sockmap: Ensure SO_RCVBUF memory is observed on ingress redirect
https://git.kernel.org/bpf/bpf/c/36cd0e696a83
- [bpf,v3,3/6] bpf, sockmap: Use truesize with sk_rmem_schedule()
https://git.kernel.org/bpf/bpf/c/70796fb751f1
- [bpf,v3,4/6] bpf, sockmap: Avoid returning unneeded EAGAIN when redirecting to self
https://git.kernel.org/bpf/bpf/c/6fa9201a8989
- [bpf,v3,5/6] bpf, sockmap: Handle memory acct if skb_verdict prog redirects to self
https://git.kernel.org/bpf/bpf/c/2443ca66676d
- [bpf,v3,6/6] bpf, sockmap: Avoid failures from skb_to_sgvec when skb has frag_list
https://git.kernel.org/bpf/bpf/c/4363023d2668
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:[~2020-11-17 23:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 22:27 [bpf PATCH v3 0/6] sockmap fixes John Fastabend
2020-11-16 22:27 ` [bpf PATCH v3 1/6] bpf, sockmap: fix partial copy_page_to_iter so progress can still be made John Fastabend
2020-11-16 22:28 ` [bpf PATCH v3 2/6] bpf, sockmap: Ensure SO_RCVBUF memory is observed on ingress redirect John Fastabend
2020-11-16 22:28 ` [bpf PATCH v3 3/6] bpf, sockmap: Use truesize with sk_rmem_schedule() John Fastabend
2020-11-16 22:28 ` [bpf PATCH v3 4/6] bpf, sockmap: Avoid returning unneeded EAGAIN when redirecting to self John Fastabend
2020-11-16 22:29 ` [bpf PATCH v3 5/6] bpf, sockmap: Handle memory acct if skb_verdict prog redirects " John Fastabend
2020-11-17 8:21 ` Jakub Sitnicki
2020-11-16 22:29 ` [bpf PATCH v3 6/6] bpf, sockmap: Avoid failures from skb_to_sgvec when skb has frag_list John Fastabend
2020-11-17 23:20 ` 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=160565520577.16897.8462803955194787332.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=jakub@cloudflare$(echo .)com \
--cc=john.fastabend@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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