From: Michal Hocko <mhocko@suse.com>
To: Zhiguo Jiang <justinjiang@vivo.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Shakeel Butt <shakeel.butt@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, opensource.kernel@vivo.com
Subject: Re: [PATCH] mm: memcg supports freeing the specified zone's memory
Date: Thu, 16 Jan 2025 15:36:27 +0100 [thread overview]
Message-ID: <Z4kZa0BLH6jexJf1@tiehlicka> (raw)
In-Reply-To: <20250116142242.615-1-justinjiang@vivo.com>
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
next prev parent reply other threads:[~2025-01-16 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 14:22 [PATCH] mm: memcg supports freeing the specified zone's memory Zhiguo Jiang
2025-01-16 14:36 ` Michal Hocko [this message]
2025-01-17 4:41 ` zhiguojiang
2025-01-17 9:33 ` Michal Hocko
2025-01-17 10:25 ` zhiguojiang
2025-01-17 11:43 ` Michal Hocko
2025-01-20 1:22 ` zhiguojiang
2025-01-20 9:40 ` Michal Hocko
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=Z4kZa0BLH6jexJf1@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=justinjiang@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=opensource.kernel@vivo.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
/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.