[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aWb6FYTMJLsvDuTy@MiWiFi-R3L-srv>
Date: Wed, 14 Jan 2026 10:06:13 +0800
From: Baoquan He <bhe@...hat.com>
To: Robin Murphy <robin.murphy@....com>
Cc: m.szyprowski@...sung.com, akpm@...ux-foundation.org, vbabka@...e.cz,
david@...nel.org, iommu@...ts.linux-foundation.org,
linux-mm@...ck.org, vladimir.kondratiev@...ileye.com,
s-adivi@...com, linux-kernel@...r.kernel.org,
lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com,
rppt@...nel.org, surenb@...gle.com, mhocko@...e.com,
jackmanb@...gle.com, hannes@...xchg.org, ziy@...dia.com
Subject: Re: [PATCH 0/3] dma-mapping: Improve atomic pool behaviour
On 01/12/26 at 03:46pm, Robin Murphy wrote:
> Hi all,
>
> 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.
Reviewed-by: Baoquan He <bhe@...hat.com>
Powered by blists - more mailing lists