From: Marek Szyprowski <m.szyprowski@samsung.com>
To: Robin Murphy <robin.murphy@arm.com>,
akpm@linux-foundation.org, vbabka@suse.cz, david@kernel.org
Cc: bhe@redhat.com, iommu@lists.linux-foundation.org,
linux-mm@kvack.org, vladimir.kondratiev@mobileye.com,
s-adivi@ti.com, linux-kernel@vger.kernel.org,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com
Subject: Re: [PATCH 0/3] dma-mapping: Improve atomic pool behaviour
Date: Tue, 13 Jan 2026 23:59:05 +0100 [thread overview]
Message-ID: <643b75da-d673-4106-888f-7fe232dccf7b@samsung.com> (raw)
In-Reply-To: <cover.1768230104.git.robin.murphy@arm.com>
On 12.01.2026 16:46, Robin Murphy wrote:
> These days we have somewhat of a matrix of mm zones that may or may not
> exist and may or may not be empty, which the per-zone atomic pool logic
> doesn't actually handle all that well. It's not all that difficult to
> improve robustness and reduce redundancy, so that's what this series
> aims for.
>
> I initially wrote this just because I happened to be looking through the
> boot log of one of my boards and had one of those out-of-the-blue
> realisations of "hang on, why *is* it allocating pools for zones it
> doesn't even have memory in?", but coincidentally, it seems that others
> happened to notice related aspects around the same time[1][2]. This is
> my attempt to sort it all out properly.
>
> I guess this could go via either the dma-mapping or mm tree, whichever
> maintainers prefer.
I will take this patchset to dma-mapping-fixes branch, thanks!
Best regards
--
Marek Szyprowski, PhD
Samsung R&D Institute Poland
next prev parent reply other threads:[~2026-01-13 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260112154649eucas1p265e59d616343bb4c2ce80128c393f56b@eucas1p2.samsung.com>
2026-01-12 15:46 ` Robin Murphy
2026-01-12 15:46 ` [PATCH 1/3] dma/pool: Improve pool lookup Robin Murphy
2026-01-12 15:46 ` [PATCH 2/3] mm_zone: Generalise has_managed_dma() Robin Murphy
2026-01-12 19:32 ` David Hildenbrand (Red Hat)
2026-01-12 15:46 ` [PATCH 3/3] dma/pool: Avoid allocating redundant pools Robin Murphy
2026-01-13 10:16 ` Baoquan He
2026-01-13 16:14 ` Robin Murphy
2026-01-14 2:05 ` Baoquan He
2026-01-13 14:07 ` [PATCH 0/3] dma-mapping: Improve atomic pool behaviour Vladimir Kondratiev
2026-01-13 22:59 ` Marek Szyprowski [this message]
2026-01-14 2:06 ` Baoquan He
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=643b75da-d673-4106-888f-7fe232dccf7b@samsung.com \
--to=m.szyprowski@samsung.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jackmanb@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=s-adivi@ti.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=vladimir.kondratiev@mobileye.com \
--cc=ziy@nvidia.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