From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>,
Caleb Sander Mateos <csander@purestorage.com>,
Stefan Metzmacher <metze@samba.org>
Subject: Re: [PATCH v2 0/13] io_uring: add IORING_OP_BPF for extending io_uring
Date: Thu, 19 Mar 2026 18:27:41 +0800 [thread overview]
Message-ID: <abvPnUeugDc5ndpL@fedora> (raw)
In-Reply-To: <8dc16ad6-f329-40de-b7f8-6bf051df3d35@kernel.dk>
On Wed, Mar 18, 2026 at 01:04:23PM -0600, Jens Axboe wrote:
> On 1/6/26 3:11 AM, Ming Lei wrote:
> > Hello,
> >
> > Add IORING_OP_BPF for extending io_uring operations, follows typical cases:
> >
> > - buffer registered zero copy [1]
> >
> > Also there are some RAID like ublk servers which needs to generate data
> > parity in case of ublk zero copy
> >
> > - extend io_uring operations from application
> >
> > Easy to add one new syscall with IORING_OP_BPF
> >
> > - extend 64 byte SQE
> >
> > bpf map can store IO data conveniently
> >
> > - communicate in IO chain
> >
> > IORING_OP_BPF can be used for communicate among IOs seamlessly without requiring
> > extra syscall
> >
> > - pretty handy to inject error for test purpose
> >
> > Any comments & feedback are welcome!
>
> Ming, can you respin your series against the current tree?
OK, I will post V3 for review.
Thanks,
Ming
prev parent reply other threads:[~2026-03-19 10:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 10:11 [PATCH v2 0/13] io_uring: add IORING_OP_BPF for extending io_uring Ming Lei
2026-01-06 10:11 ` [PATCH V2 01/13] io_uring: make io_import_fixed() global Ming Lei
2026-01-06 10:11 ` [PATCH V2 02/13] io_uring: refactor io_prep_reg_iovec() for BPF kfunc use Ming Lei
2026-01-06 10:11 ` [PATCH V2 03/13] io_uring: refactor io_import_reg_vec() " Ming Lei
2026-01-06 10:11 ` [PATCH V2 04/13] io_uring: prepare for extending io_uring with bpf Ming Lei
2026-01-06 10:11 ` [PATCH V2 05/13] io_uring: bpf: extend io_uring with bpf struct_ops Ming Lei
2026-01-06 10:11 ` [PATCH V2 06/13] io_uring: bpf: implement struct_ops registration Ming Lei
2026-01-06 10:11 ` [PATCH V2 07/13] io_uring: bpf: add BPF buffer descriptor for IORING_OP_BPF Ming Lei
2026-01-06 10:11 ` [PATCH V2 08/13] io_uring: bpf: add uring_bpf_memcpy() kfunc Ming Lei
2026-03-14 5:18 ` Caleb Sander Mateos
2026-03-16 13:38 ` Ming Lei
2026-01-06 10:11 ` [PATCH V2 09/13] selftests/io_uring: update mini liburing Ming Lei
2026-01-06 10:11 ` [PATCH V2 10/13] selftests/io_uring: add BPF struct_ops and kfunc tests Ming Lei
2026-01-06 10:11 ` [PATCH V2 11/13] selftests/io_uring: add bpf_memcpy selftest for uring_bpf_memcpy() kfunc Ming Lei
2026-01-06 10:11 ` [PATCH V2 12/13] selftests/io_uring: add copy_user_to_fixed() and copy_fixed_to_user() bpf_memcpy tests Ming Lei
2026-01-06 10:11 ` [PATCH V2 13/13] selftests/io_uring: add copy_user_to_reg_vec() and copy_reg_vec_to_user() " Ming Lei
2026-03-18 19:04 ` [PATCH v2 0/13] io_uring: add IORING_OP_BPF for extending io_uring Jens Axboe
2026-03-19 10:27 ` Ming Lei [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=abvPnUeugDc5ndpL@fedora \
--to=ming.lei@redhat.com \
--cc=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=io-uring@vger.kernel.org \
--cc=metze@samba.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