[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9b5b669-0318-93c8-c6a0-dbbb797320f2@quicinc.com>
Date: Fri, 5 Jan 2024 15:46:55 -0800
From: Sukadev Bhattiprolu <quic_sukadev@...cinc.com>
To: Minchan Kim <minchan@...nel.org>,
Chris Goldsworthy
<quic_cgoldswo@...cinc.com>
CC: Roman Gushchin <roman.gushchin@...ux.dev>,
Andrew Morton
<akpm@...ux-foundation.org>,
Rik van Riel <riel@...riel.com>, Roman Gushchin
<guro@...com>,
Vlastimil Babka <vbabka@...e.cz>, Joonsoo Kim
<js1304@...il.com>,
Georgi Djakov <quic_c_gdjako@...cinc.com>, <linux-mm@...ck.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm,page_alloc,cma: configurable CMA utilization
On 2/1/2023 3:47 PM, Minchan Kim wrote:
>
> I like this patch for different reason but for the specific problem you
> mentioned, How about making reclaimer/compaction aware of the problem:
>
> IOW, when the GFP_KERNEL/DMA allocation happens but not enough memory
> in the zones, let's migrates movable pages in those zones into CMA
> area/movable zone if they are plenty of free memory.
Hi Minchan,
Coming back to this thread after a while.
If the CMA region is usually free, allocating pages first in the non-CMA
region and then moving them into the CMA region would be extra work since
it would happen most of the time. In such cases, wouldn't it be better to
allocate from the CMA region itself?
Sukadev
Powered by blists - more mailing lists