From: Kanchan Joshi <[email protected]>
To: Keith Busch <[email protected]>,
[email protected], [email protected],
[email protected]
Cc: [email protected], [email protected], [email protected],
[email protected], Keith Busch <[email protected]>
Subject: Re: [PATCHv4 1/4] block: bio-integrity: directly map user buffers
Date: Wed, 29 Nov 2023 20:48:41 +0530 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 11/29/2023 3:57 AM, Keith Busch wrote:
> If the user address can't directly be used for reason, like too many
> segments or address unalignement, fallback to a copy of the user vec
> while keeping the user address pinned for the IO duration so that it
> can safely be copied on completion in any process context.
The pinning requirement is only for read. But code keeps user-memory
pinned for write too. Is there any reason?
next prev parent reply other threads:[~2023-11-29 15:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 22:27 [PATCHv4 0/4] block integrity: directly map user space addresses Keith Busch
2023-11-28 22:27 ` [PATCHv4 1/4] block: bio-integrity: directly map user buffers Keith Busch
2023-11-29 15:18 ` Kanchan Joshi [this message]
2023-11-29 16:35 ` Keith Busch
2023-11-28 22:27 ` [PATCHv4 2/4] nvme: use bio_integrity_map_user Keith Busch
2023-11-28 22:27 ` [PATCHv4 3/4] iouring: remove IORING_URING_CMD_POLLED Keith Busch
2023-11-28 22:27 ` [PATCHv4 4/4] io_uring: remove uring_cmd cookie Keith Busch
2023-11-29 1:37 ` [PATCHv4 0/4] block integrity: directly map user space addresses Martin K. Petersen
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] \
[email protected] \
[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