From: patchwork-bot+netdevbpf@kernel.org
To: John Fastabend <john.fastabend@gmail.com>
Cc: alexei.starovoitov@gmail.com, daniel@iogearbox.net,
netdev@vger.kernel.org, bpf@vger.kernel.org,
jakub@cloudflare.com, lmb@cloudflare.com
Subject: Re: [bpf-next PATCH v2 0/6] sockmap/sk_skb program memory acct fixes
Date: Mon, 12 Oct 2020 01:10:03 +0000 [thread overview]
Message-ID: <160246500365.4244.11580231205636613123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <160226839426.5692.13107801574043388675.stgit@john-Precision-5820-Tower>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Fri, 09 Oct 2020 11:35:53 -0700 you wrote:
> Users of sockmap and skmsg trying to build proxys and other tools
> have pointed out to me the error handling can be problematic. If
> the proxy is under-provisioned and/or the BPF admin does not have
> the ability to update/modify memory provisions on the sockets
> its possible data may be dropped. For some things we have retries
> so everything works out OK, but for most things this is likely
> not great. And things go bad.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/6] bpf, sockmap: skb verdict SK_PASS to self already checked rmem limits
https://git.kernel.org/bpf/bpf-next/c/cfea28f890cf
- [bpf-next,v3,2/6] bpf, sockmap: On receive programs try to fast track SK_PASS ingress
https://git.kernel.org/bpf/bpf-next/c/9ecbfb06a078
- [bpf-next,v3,3/6] bpf, sockmap: remove skb_set_owner_w wmem will be taken later from sendpage
https://git.kernel.org/bpf/bpf-next/c/29545f4977cf
- [bpf-next,v3,4/6] bpf, sockmap: remove dropped data on errors in redirect case
https://git.kernel.org/bpf/bpf-next/c/9047f19e7ccb
- [bpf-next,v3,5/6] bpf, sockmap: Remove skb_orphan and let normal skb_kfree do cleanup
https://git.kernel.org/bpf/bpf-next/c/10d58d006356
- [bpf-next,v3,6/6] bpf, sockmap: Add memory accounting so skbs on ingress lists are visible
https://git.kernel.org/bpf/bpf-next/c/0b17ad25d8d1
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-10-12 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 18:35 [bpf-next PATCH v2 0/6] sockmap/sk_skb program memory acct fixes John Fastabend
2020-10-09 18:36 ` [bpf-next PATCH v3 1/6] bpf, sockmap: skb verdict SK_PASS to self already checked rmem limits John Fastabend
2020-10-09 18:36 ` [bpf-next PATCH v3 2/6] bpf, sockmap: On receive programs try to fast track SK_PASS ingress John Fastabend
2020-10-12 9:03 ` Jakub Sitnicki
2020-10-12 15:33 ` John Fastabend
2020-10-13 19:43 ` Jakub Sitnicki
2020-10-09 18:36 ` [bpf-next PATCH v3 3/6] bpf, sockmap: remove skb_set_owner_w wmem will be taken later from sendpage John Fastabend
2020-10-09 18:37 ` [bpf-next PATCH v3 4/6] bpf, sockmap: remove dropped data on errors in redirect case John Fastabend
2020-10-12 12:04 ` Jakub Sitnicki
2020-10-12 17:19 ` John Fastabend
2020-10-13 10:27 ` Jakub Sitnicki
2020-10-09 18:37 ` [bpf-next PATCH v3 5/6] bpf, sockmap: Remove skb_orphan and let normal skb_kfree do cleanup John Fastabend
2020-10-09 18:37 ` [bpf-next PATCH v3 6/6] bpf, sockmap: Add memory accounting so skbs on ingress lists are visible John Fastabend
2020-10-12 1:10 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-09 17:57 [bpf-next PATCH v2 0/6] sockmap/sk_skb program memory acct fixes John Fastabend
2020-10-09 18:04 ` John Fastabend
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=160246500365.4244.11580231205636613123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=lmb@cloudflare.com \
--cc=netdev@vger.kernel.org \
/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).