From: Jens Axboe <[email protected]>
To: Gabriel Krisman Bertazi <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] io_uring/rsrc: Drop io_copy_iov in favor of iovec API
Date: Sat, 25 May 2024 10:09:46 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, 23 May 2024 17:45:35 -0400, Gabriel Krisman Bertazi wrote:
> Instead of open coding an io_uring function to copy iovs from userspace,
> rely on the existing iovec_from_user function. While there, avoid
> repeatedly zeroing the iov in the !arg case for io_sqe_buffer_register.
>
> tested with liburing testsuite.
>
>
> [...]
Applied, thanks!
[1/1] io_uring/rsrc: Drop io_copy_iov in favor of iovec API
commit: 96b170eb1ebe2be0bb2e55e825b876e18bb70293
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-05-25 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 21:45 [PATCH] io_uring/rsrc: Drop io_copy_iov in favor of iovec API Gabriel Krisman Bertazi
2024-05-25 16:09 ` 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=171665338621.160479.12908327797304327838.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