From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Cc: bpf@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH v10 0/4] BPF controlled io_uring
Date: Tue, 17 Mar 2026 14:36:57 -0600 [thread overview]
Message-ID: <177377981764.1008333.17403039550067431801.b4-ty@kernel.dk> (raw)
In-Reply-To: <cover.1772109579.git.asml.silence@gmail.com>
On Thu, 26 Feb 2026 12:48:37 +0000, Pavel Begunkov wrote:
> 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.
>
> There are multiple use cases I want to cover with this:
>
> - Syscall avoidance. Instead of returning to the userspace for
> CQE processing, a part of the logic can be moved into BPF to
> avoid excessive number of syscalls.
>
> [...]
Applied, thanks!
[1/4] io_uring: introduce callback driven main loop
commit: 033af2b3eb19c5ed96825572105bca3611635ada
[2/4] io_uring/bpf-ops: implement loop_step with BPF struct_ops
commit: d0e437b76bd3c979ddaa6205f5e9ad3e0f95faef
[3/4] io_uring/bpf-ops: add kfunc helpers
commit: 890819248a8616558fe12e6c06c918ee1c3a2bc6
[4/4] io_uring/bpf-ops: implement bpf ops registration
commit: 98f37634b12b17ad5c56db8fb63cf9d7dc55d74c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-03-17 20:37 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
2026-03-16 22:13 ` Jens Axboe
2026-03-17 20:36 ` Jens Axboe [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=177377981764.1008333.17403039550067431801.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=ast@kernel.org \
--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