From: Keith Busch <kbusch@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org,
Leon Romanovsky <leon@kernel.org>,
Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
Subject: Re: [PATCH] nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary
Date: Wed, 4 Dec 2024 09:26:05 -0800 [thread overview]
Message-ID: <Z1CQrRd2F04MvsLT@kbusch-mbp> (raw)
In-Reply-To: <20241204004240.687875-1-hch@lst.de>
On Wed, Dec 04, 2024 at 09:42:40AM +0900, Christoph Hellwig wrote:
> Only call into nvme_alloc_host_mem_single which uses
> dma_alloc_noncontiguous when there is non-null dma merge boundary.
> Without this we'll call into dma_alloc_noncontiguous for device using
> dma-direct, which can work fine as long as the preferred size is below the
> MAX_ORDER of the page allocator, but blows up with a warning if it is
> too large.
Thanks, applied to nvme-6.13 with the mentioned spelling fix.
prev parent reply other threads:[~2024-12-04 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 0:42 [PATCH] nvme-pci: don't use dma_alloc_noncontiguous with 0 merge boundary Christoph Hellwig
2024-12-04 1:36 ` Jens Axboe
2024-12-05 0:20 ` Christoph Hellwig
2024-12-04 8:45 ` Borah, Chaitanya Kumar
2024-12-04 8:55 ` Leon Romanovsky
2024-12-04 17:26 ` Keith Busch [this message]
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=Z1CQrRd2F04MvsLT@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=hch@lst.de \
--cc=leon@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