mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* fix nvme performance regression due to dma_max_mapping_size()
@ 2019-07-17  6:26 Christoph Hellwig
  2019-07-17  6:26 ` [PATCH 1/2] dma-mapping: add a dma_addressing_limited helper Christoph Hellwig
  2019-07-17  6:26 ` [PATCH 2/2] dma-direct: only limit the mapping size if swiotlb could be used Christoph Hellwig
  0 siblings, 2 replies; 3+ messages in thread
From: Christoph Hellwig @ 2019-07-17  6:26 UTC (permalink / raw)
  To: iommu; +Cc: Joerg Roedel, Benjamin Herrenschmidt, linux-kernel

Hi all,

the new dma_max_mapping_size function is a little to eager to limit
the I/O size if the swiotlb buffer is present, but the device is
not addressing limited.  Fix this by adding an additional check.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-07-17  6:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-17  6:26 fix nvme performance regression due to dma_max_mapping_size() Christoph Hellwig
2019-07-17  6:26 ` [PATCH 1/2] dma-mapping: add a dma_addressing_limited helper Christoph Hellwig
2019-07-17  6:26 ` [PATCH 2/2] dma-direct: only limit the mapping size if swiotlb could be used Christoph Hellwig

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®