Message ID | 20200226083719.4389-1-bob.liu@oracle.com (mailing list archive) |
---|---|
Headers | show |
Series | userspace PI passthrough via io_uring | expand |
On 2/26/20 1:37 AM, Bob Liu wrote: > This RFC provides a rough implementation of a mechanism to allow > userspace to attach protection information (e.g. T10 DIF) data to a > disk write and to receive the information alongside a disk read. > The interface is an extension to the io_uring interface: > two new commands (IORING_OP_READV{WRITEV}_PI) are provided. > The last struct iovec in the arg list is interpreted to point to a buffer > containing the the PI data. > > Patch #1 add two new commands to io_uring. > Patch #2 introduces two helper funcs in bio-integrity. > Patch #3 implement the PI passthrough in direct-io of block-dev. > (Similar extensions may add to fs/direct-io.c and fs/maps/directio.c) > Patch #4 add io_uring use space test case to liburing. No strong feelings on the support in general, the io_uring bits are trivial enough (once fixed up, per comments in that patch) that I have no objections on that front. I'd really like Martin to render an opinion on the API (PI info in last vec), since he's the integrity guy.