public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH v4 0/9] Add support for vectored registered buffers
Date: Fri, 07 Mar 2025 09:40:05 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>


On Fri, 07 Mar 2025 16:00:28 +0000, Pavel Begunkov wrote:
> Add registered buffer support for vectored io_uring operations. That
> allows to pass an iovec, all entries of which must belong to and
> point into the same registered buffer specified by sqe->buf_index.
> 
> The series covers zerocopy sendmsg and reads / writes. Reads and
> writes are implemented as new opcodes, while zerocopy sendmsg
> reuses IORING_RECVSEND_FIXED_BUF for the user API.
> 
> [...]

Applied, thanks!

[1/9] io_uring: introduce struct iou_vec
      commit: e1d499590977a492ae120d9263bd55076aabd460
[2/9] io_uring: add infra for importing vectored reg buffers
      commit: 9ef4cbbcb4ac3786a1a4164507511b76b2a572c5
[3/9] io_uring/rw: implement vectored registered rw
      commit: bdabba04bb1023e0327998b1eb0be096079bde65
[4/9] io_uring/rw: defer reg buf vec import
      commit: 835c4bdf95d5c71fd5b41f77f2343b695b4494aa
[5/9] io_uring/net: combine msghdr copy
      commit: 7fc9b27f8ee940ebb4035957e15225732e106d09
[6/9] io_uring/net: pull vec alloc out of msghdr import
      commit: ae89ab8845288c751a3cc7f3215cb44ec6a900f7
[7/9] io_uring/net: convert to struct iou_vec
      commit: 8066b67a8a0c4fdf93c043698c36474cc1fc0ff7
[8/9] io_uring/net: implement vectored reg bufs for zctx
      commit: c983552d59531792533191186def14ea34d80590
[9/9] io_uring: cap cached iovec/bvec size
      commit: 89176d5837668a429d862c9aff392226026ae7b3

Best regards,
-- 
Jens Axboe




      parent reply	other threads:[~2025-03-07 16:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 16:00 [PATCH v4 0/9] Add support for vectored registered buffers Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 1/9] io_uring: introduce struct iou_vec Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 2/9] io_uring: add infra for importing vectored reg buffers Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 3/9] io_uring/rw: implement vectored registered rw Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 4/9] io_uring/rw: defer reg buf vec import Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 5/9] io_uring/net: combine msghdr copy Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 6/9] io_uring/net: pull vec alloc out of msghdr import Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 7/9] io_uring/net: convert to struct iou_vec Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 8/9] io_uring/net: implement vectored reg bufs for zctx Pavel Begunkov
2025-03-07 16:00 ` [PATCH v4 9/9] io_uring: cap cached iovec/bvec size Pavel Begunkov
2025-03-07 16:40 ` 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=174136560593.394257.3485449892877220935.b4-ty@kernel.dk \
    [email protected] \
    [email protected] \
    [email protected] \
    /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