[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4kZa0BLH6jexJf1@tiehlicka>
Date: Thu, 16 Jan 2025 15:36:27 +0100
From: Michal Hocko <mhocko@...e.com>
To: Zhiguo Jiang <justinjiang@...o.com>
Cc: Johannes Weiner <hannes@...xchg.org>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Shakeel Butt <shakeel.butt@...ux.dev>,
Muchun Song <muchun.song@...ux.dev>,
Andrew Morton <akpm@...ux-foundation.org>, cgroups@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
opensource.kernel@...o.com
Subject: Re: [PATCH] mm: memcg supports freeing the specified zone's memory
On Thu 16-01-25 22:22:42, Zhiguo Jiang wrote:
> Currently, the try_to_free_mem_cgroup_pages interface releases the
> memory occupied by the memcg, which defaults to all zones in the system.
> However, for multi zone systems, such as when there are both movable zone
> and normal zone, it is not possible to release memory that is only in
> the normal zone.
>
> This patch is used to implement the try_to_free_mem_cgroup_pages interface
> to support for releasing the specified zone's memory occupied by the
> memcg in a multi zone systems, in order to optimize the memory usage of
> multiple zones.
Could you elaborate more on the actual usecase please? Who is going to
control which zone to reclaim from, how and why?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists