From: Pavel Begunkov <asml.silence@gmail.com>
To: Caleb Sander Mateos <csander@purestorage.com>
Cc: io-uring@vger.kernel.org, bpf@vger.kernel.org, axboe@kernel.dk,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH v10 0/4] BPF controlled io_uring
Date: Mon, 16 Mar 2026 14:11:10 +0000 [thread overview]
Message-ID: <6d2a9643-962a-4328-b8e1-3bd264d73d19@gmail.com> (raw)
In-Reply-To: <CADUfDZoBTwnCo-f_st9-jdgNhHLWUCjZQFpGdowGUA5BoJ836w@mail.gmail.com>
On 3/9/26 15:02, Caleb Sander Mateos wrote:
> On Mon, Mar 9, 2026 at 6:24 AM Pavel Begunkov <asml.silence@gmail.com> wrote:
...
>>> - Smarter polling. Napi polling is performed only once per syscall
>>> and then it switches to waiting. We can do smarter and intermix
>>> polling with waiting using the hook.
>>
>> Any comments for the patch set?
>
> I'm not opposed to this feature, but I agree with Ming that it seems
> largely orthogonal to his patchset allowing BPF programs to access
> io_uring registered buffers[1]. This patchset doesn't provide any
The idea of giving BPF access to registered buffers is largely
orthogonal to underlying ops implementation, I agree.
> kfuncs for interacting with registered buffers, so we would still need
> something like the kfuncs implemented by Ming's patchset to allow BPF
> programs to access registered buffers directly. Although either the
Surely
> ->loop_step() or ->prep()/->issue() interface could allow userspace to
> run a BPF program in the context of the io_uring, I wouldn't be keen
> on reimplementing the entire io_uring_enter() loop logic just to
> intercept a few requests to run BPF programs.
I don't think some 50 or maybe fewer lines of generic code is that
much of a hassle, I'm thinking about adding it as a library code of
some sort. In either case, I'm not trying to convince you to do more
work.
--
Pavel Begunkov
next prev parent reply other threads:[~2026-03-16 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 12:48 [PATCH v10 0/4] BPF controlled io_uring Pavel Begunkov
2026-02-26 12:48 ` [PATCH v10 1/4] io_uring: introduce callback driven main loop Pavel Begunkov
2026-02-26 12:48 ` [PATCH v10 2/4] io_uring/bpf-ops: implement loop_step with BPF struct_ops Pavel Begunkov
2026-02-26 12:48 ` [PATCH v10 3/4] io_uring/bpf-ops: add kfunc helpers Pavel Begunkov
2026-02-26 12:48 ` [PATCH v10 4/4] io_uring/bpf-ops: implement bpf ops registration Pavel Begunkov
2026-03-09 13:24 ` [PATCH v10 0/4] BPF controlled io_uring Pavel Begunkov
2026-03-09 15:02 ` Caleb Sander Mateos
2026-03-16 14:11 ` Pavel Begunkov [this message]
2026-03-16 22:13 ` Jens Axboe
2026-03-17 20:36 ` Jens Axboe
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=6d2a9643-962a-4328-b8e1-3bd264d73d19@gmail.com \
--to=asml.silence@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=axboe@kernel.dk \
--cc=bpf@vger.kernel.org \
--cc=csander@purestorage.com \
--cc=io-uring@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