From: Jakub Sitnicki <jakub@cloudflare.com>
To: John Fastabend <john.fastabend@gmail.com>
Cc: daniel@iogearbox.net, bpf@vger.kernel.org,
netdev@vger.kernel.org, edumazet@google.com, ast@kernel.org,
andrii@kernel.org, will@isovalent.com
Subject: Re: [PATCH bpf v8 03/13] bpf: sockmap, reschedule is now done through backlog
Date: Wed, 17 May 2023 11:12:48 +0200 [thread overview]
Message-ID: <87r0rf8gnj.fsf@cloudflare.com> (raw)
In-Reply-To: <20230517052244.294755-4-john.fastabend@gmail.com>
On Tue, May 16, 2023 at 10:22 PM -07, John Fastabend wrote:
> Now that the backlog manages the reschedule() logic correctly we can drop
> the partial fix to reschedule from recvmsg hook.
>
> Rescheduling on recvmsg hook was added to address a corner case where we
> still had data in the backlog state but had nothing to kick it and
> reschedule the backlog worker to run and finish copying data out of the
> state. This had a couple limitations, first it required user space to
> kick it introducing an unnecessary EBUSY and retry. Second it only
> handled the ingress case and egress redirects would still be hung.
>
> With the correct fix, pushing the reschedule logic down to where the
> enomem error occurs we can drop this fix.
>
> Reviewed-by: Reviewed-by: Jakub Sitnicki <jakub@cloudflare.com>
Something went wrong here.
> Fixes: bec217197b412 ("skmsg: Schedule psock work if the cached skb exists on the psock")
> Signed-off-by: John Fastabend <john.fastabend@gmail.com>
> ---
[...]
next prev parent reply other threads:[~2023-05-17 9:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 5:22 [PATCH bpf v8 00/13] bpf sockmap fixes John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 01/13] bpf: sockmap, pass skb ownership through read_skb John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 02/13] bpf: sockmap, convert schedule_work into delayed_work John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 03/13] bpf: sockmap, reschedule is now done through backlog John Fastabend
2023-05-17 9:12 ` Jakub Sitnicki [this message]
2023-05-17 5:22 ` [PATCH bpf v8 04/13] bpf: sockmap, improved check for empty queue John Fastabend
2023-05-17 9:44 ` Jakub Sitnicki
2023-05-17 5:22 ` [PATCH bpf v8 05/13] bpf: sockmap, handle fin correctly John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 06/13] bpf: sockmap, TCP data stall on recv before accept John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 07/13] bpf: sockmap, wake up polling after data copy John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 08/13] bpf: sockmap, incorrectly handling copied_seq John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 09/13] bpf: sockmap, pull socket helpers out of listen test for general use John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 10/13] bpf: sockmap, build helper to create connected socket pair John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 11/13] bpf: sockmap, test shutdown() correctly exits epoll and recv()=0 John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 12/13] bpf: sockmap, test FIONREAD returns correct bytes in rx buffer John Fastabend
2023-05-17 5:22 ` [PATCH bpf v8 13/13] bpf: sockmap, test FIONREAD returns correct bytes in rx buffer with drops John Fastabend
2023-05-17 13:54 ` [PATCH bpf v8 00/13] bpf sockmap fixes Daniel Borkmann
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=87r0rf8gnj.fsf@cloudflare.com \
--to=jakub@cloudflare.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=will@isovalent.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).