From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>, io-uring@vger.kernel.org
Cc: bpf@vger.kernel.org, Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: Re: [PATCH io_uring-7.1 v6 0/5] BPF controlled io_uring
Date: Mon, 16 Feb 2026 08:18:42 -0700 [thread overview]
Message-ID: <ab4c6ffd-d7d2-45fc-bbd5-b6663d5c41e2@kernel.dk> (raw)
In-Reply-To: <d56b5f70-382e-4017-81f4-c9ae7a6c1b56@gmail.com>
On 2/16/26 7:23 AM, Pavel Begunkov wrote:
> On 2/11/26 19:04, Pavel Begunkov wrote:
>> This series introduces a way to override the standard io_uring_enter
>> syscall execution with an extendible event loop, which can be controlled
>> by BPF via new io_uring struct_ops or from within the kernel.
>
> Let me know if there are any concerns or comments. There are some
> parts that I'll need to add like timeouts for waiting, but those
> will be natural extensions, and this feels like a good base to
> move forward in general.
I don't have any complaints on it, but would be good to hear from the
BPF folks.
--
Jens Axboe
next prev parent reply other threads:[~2026-02-16 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 19:04 [PATCH io_uring-7.1 v6 0/5] BPF controlled io_uring Pavel Begunkov
2026-02-11 19:04 ` [PATCH v6 1/5] io_uring: introduce callback driven main loop Pavel Begunkov
2026-02-16 15:49 ` Jens Axboe
2026-02-11 19:04 ` [PATCH v6 2/5] io_uring/bpf-ops: implement loop_step with BPF struct_ops Pavel Begunkov
2026-02-11 19:04 ` [PATCH v6 3/5] io_uring/bpf-ops: add kfunc helpers Pavel Begunkov
2026-02-11 19:04 ` [PATCH v6 4/5] io_uring/bpf-ops: implement bpf ops registration Pavel Begunkov
2026-02-11 19:04 ` [PATCH v6 5/5] selftests/io_uring: add a bpf io_uring selftest Pavel Begunkov
2026-02-16 14:23 ` [PATCH io_uring-7.1 v6 0/5] BPF controlled io_uring Pavel Begunkov
2026-02-16 15:18 ` Jens Axboe [this message]
2026-02-17 11:29 ` Pavel Begunkov
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=ab4c6ffd-d7d2-45fc-bbd5-b6663d5c41e2@kernel.dk \
--to=axboe@kernel.dk \
--cc=alexei.starovoitov@gmail.com \
--cc=asml.silence@gmail.com \
--cc=bpf@vger.kernel.org \
--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