From: Jens Axboe <[email protected]>
To: Xiaoguang Wang <[email protected]>,
[email protected]
Cc: [email protected]
Subject: Re: [PATCH] io_uring: do not always copy iovec in io_req_map_rw()
Date: Wed, 8 Apr 2020 08:24:12 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/8/20 7:29 AM, Xiaoguang Wang wrote:
> In io_read_prep() or io_write_prep(), io_req_map_rw() takes
> struct io_async_rw's fast_iov as argument to call io_import_iovec(),
> and if io_import_iovec() uses struct io_async_rw's fast_iov as
> valid iovec array, later indeed io_req_map_rw() does not need
> to do the memcpy operation, because they are same pointers.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-04-08 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-08 14:29 [PATCH] io_uring: do not always copy iovec in io_req_map_rw() Xiaoguang Wang
2020-04-08 15:24 ` 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 \
[email protected] \
[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