From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>
Cc: linux-nvme@lists.infradead.org
Subject: create single-segment HMBs when using IOMMU
Date: Fri, 1 Nov 2024 05:40:03 +0100 [thread overview]
Message-ID: <20241101044016.405265-1-hch@lst.de> (raw)
Hi all,
NVMe controllers usually have a limit of how many HMB descriptors they
support, and even if they support multiple they usually prefer less of
them. When running with an IOMMU, the DMA API can coalesce virtually
discontiguous segments, and using the right API doesn't even eat up
vmalloc space for that.
Diffstat:
pci.c | 74 +++++++++++++++++++++++++++++++++++++++++++++++++++++++-----------
1 file changed, 62 insertions(+), 12 deletions(-)
next reply other threads:[~2024-11-01 4:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 4:40 Christoph Hellwig [this message]
2024-11-01 4:40 ` [PATCH 1/2] nvme-pci: fix freeing of the HMB descriptor table Christoph Hellwig
2024-11-01 4:40 ` [PATCH 2/2] nvme-pci: use dma_alloc_noncontigous if possible Christoph Hellwig
2024-12-02 19:05 ` Leon Romanovsky
2024-12-02 19:15 ` Keith Busch
2024-12-02 19:20 ` Leon Romanovsky
2024-12-03 0:33 ` Christoph Hellwig
2024-11-05 15:59 ` create single-segment HMBs when using IOMMU Keith Busch
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 \
--in-reply-to=20241101044016.405265-1-hch@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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