From: Christoph Hellwig <hch@lst.de>
To: Michal Hocko <mhocko@suse.com>
Cc: Christoph Hellwig <hch@lst.de>,
iommu@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Robin Murphy <robin.murphy@arm.com>,
David Rientjes <rientjes@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] dma-pool: limit DMA and DMA32 zone size pools
Date: Mon, 22 Aug 2022 14:27:59 +0200 [thread overview]
Message-ID: <20220822122759.GA14932@lst.de> (raw)
In-Reply-To: <YwNx6Q+FSwpKUOQ2@dhcp22.suse.cz>
On Mon, Aug 22, 2022 at 02:09:13PM +0200, Michal Hocko wrote:
> OK, so you are worried about configurations that lack ZONE_DMA32 because
> that memory range is covered by ZONE_DMA? I thought though simply do not
> have CONFIG_ZONE_DMA32. Or am I wrong here?
Zones can disappear when they are empty. Normally that affects
ZONE_NORMAL and ZONE_HIGHMEM, but it can also happen to ZONE_DMA32
when there is not enough memory.
next prev parent reply other threads:[~2022-08-22 12:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 6:06 fix dma coherent pool sizing Christoph Hellwig
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 [this message]
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
2022-08-22 6:12 ` [PATCH 3/3] dma-pool: limit DMA and DMA32 zone size pools 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=20220822122759.GA14932@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.