lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z4okBYrYD8G1WdKx@tiehlicka>
Date: Fri, 17 Jan 2025 10:33:57 +0100
From: Michal Hocko <mhocko@...e.com>
To: zhiguojiang <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 Fri 17-01-25 12:41:40, zhiguojiang wrote:
[...]
> In response to the above situation, we need reclaim only the normal
> zone's memory occupied by memcg by try_to_free_mem_cgroup_pages(), in
> order to solve the issues of the gfp flags allocations and failure due
> to gfp flags limited only to alloc memory from the normal zone. At this
> point, if the memcg memory reclaimed by try_to_free_mem_cgroup_pages()
> mainly comes from the movable zone, which cannot solve such problems.

Memory cgroup reclaim doesn't allocate the memory directly. This is done
by the page allocator called before the memory is charged. The memcg
charging is then responsible for reclaiming charges and that is not
really zone aware.

Could you describe problem that you are trying to solve?
-- 
Michal Hocko
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ