From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Cc: Caleb Sander Mateos <[email protected]>
Subject: Re: [PATCH v2 0/4] clean up rw buffer import
Date: Tue, 25 Feb 2025 07:43:39 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 24 Feb 2025 19:45:02 +0000, Pavel Begunkov wrote:
> Do some minor brushing for read/write prep. It might need more work,
> but should be a cleaner base for changes around how we import buffers.
>
> v2: void * -> struct iovec * in io_import_vec()
> flip the if branches in __io_import_rw_buffer()
>
> Pavel Begunkov (4):
> io_uring/rw: allocate async data in io_prep_rw()
> io_uring/rw: rename io_import_iovec()
> io_uring/rw: extract helper for iovec import
> io_uring/rw: open code io_prep_rw_setup()
>
> [...]
Applied, thanks!
[1/4] io_uring/rw: allocate async data in io_prep_rw()
commit: c72282dd865ee66bc1b8fbc843deefe53beb426c
[2/4] io_uring/rw: rename io_import_iovec()
commit: 74c942499917e5d011ae414a026dda00a995a09b
[3/4] io_uring/rw: extract helper for iovec import
commit: 99fab04778da20d2b7e224cb6932eb2ad532f5d8
[4/4] io_uring/rw: open code io_prep_rw_setup()
commit: 61ed48b5fc63d1c6d9c3eb59ed2b46a2cbfc6039
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-02-25 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 19:45 [PATCH v2 0/4] clean up rw buffer import Pavel Begunkov
2025-02-24 19:45 ` [PATCH v2 1/4] io_uring/rw: allocate async data in io_prep_rw() Pavel Begunkov
2025-02-24 19:45 ` [PATCH v2 2/4] io_uring/rw: rename io_import_iovec() Pavel Begunkov
2025-02-24 19:45 ` [PATCH v2 3/4] io_uring/rw: extract helper for iovec import Pavel Begunkov
2025-02-24 19:45 ` [PATCH v2 4/4] io_uring/rw: open code io_prep_rw_setup() Pavel Begunkov
2025-02-25 14:43 ` 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=174049461937.2111022.2491756232035105242.b4-ty@kernel.dk \
[email protected] \
[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