Thread (56 messages) 56 messages, 5 authors, 2025-09-08

Re: [PATCH v4 15/16] block-dma: properly take MMIO path

From: Keith Busch <kbusch@kernel.org>
Date: 2025-08-28 19:10:36
Also in: linux-block, linux-doc, linux-iommu, linux-mm, linux-nvme, linuxppc-dev, lkml, rust-for-linux, virtualization, xen-devel

On Thu, Aug 28, 2025 at 03:41:15PM -0300, Jason Gunthorpe wrote:
On Thu, Aug 28, 2025 at 11:15:20AM -0600, Keith Busch wrote:
quoted
I don't think that was ever the case. Metadata is allocated
independently of the data payload, usually by the kernel in
bio_integrity_prep() just before dispatching the request. The bio may
have a p2p data payload, but the integrity metadata is just a kmalloc
buf in that path.
Then you should do two dma mapping operations today, that is how the
API was built. You shouldn't mix P2P and non P2P within a single
operation right now..
Data and metadata are mapped as separate operations. They're just
different parts of one blk-mq request.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help