From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>
Cc: Michal Hocko <mhocko@suse.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org
Subject: fix dma coherent pool sizing
Date: Wed, 17 Aug 2022 08:06:44 +0200 [thread overview]
Message-ID: <20220817060647.1032426-1-hch@lst.de> (raw)
Hi all
Michal pointed out that the sizing of the dma coherent pools is bonkers
as it uses the total memory to size the pool for each zone, which leads
to comically larger zones for the 16-MB ZONE_DMA on x86, which tends
leads to allocation failure warnings. This series switches to sizing
the ZONE_DMA and ZONE_DMA32 pools based on the number of pages that
actually reside in those zones instead.
Diffstat:
pool.c | 65 +++++++++++++++++++++++++++++++++++++++++------------------------
1 file changed, 41 insertions(+), 24 deletions(-)
next reply other threads:[~2022-08-17 6:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 6:06 Christoph Hellwig [this message]
2022-08-17 6:06 ` [PATCH 1/3] dma-pool: factor out a calculate_pool_size helper Christoph Hellwig
2022-08-17 12:32 ` Robin Murphy
2022-08-21 10:41 ` Christoph Hellwig
2022-08-17 6:06 ` [PATCH 2/3] dma-pool: don't return errors from dma_atomic_pool_init Christoph Hellwig
2022-08-17 12:36 ` Robin Murphy
2022-08-17 6:06 ` [PATCH 3/3] dma-pool: limit DMA and DMA32 zone size pools Christoph Hellwig
2022-08-17 12:50 ` Robin Murphy
2022-08-21 10:43 ` Christoph Hellwig
2022-08-17 12:53 ` Michal Hocko
2022-08-21 10:44 ` Christoph Hellwig
2022-08-22 8:41 ` Michal Hocko
2022-08-22 11:14 ` Christoph Hellwig
2022-08-22 12:09 ` Michal Hocko
2022-08-22 12:27 ` Christoph Hellwig
2022-08-22 14:21 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2022-08-22 6:12 fix dma coherent pool sizing Christoph Hellwig
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=20220817060647.1032426-1-hch@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@suse.com \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
/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