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?
