linux-kernel - Re: [RFC -next] memcg: Optimize creation performance when LRU

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: <ef8f934d-6792-4b6d-8f47-81f78edc1e93@huaweicloud.com>
Date: Thu, 4 Dec 2025 20:59:06 +0800
From: Chen Ridong <chenridong@...weicloud.com>
To: Johannes Weiner <hannes@...xchg.org>, Yu Zhao <yuzhao@...gle.com>
Cc: akpm@...ux-foundation.org, david@...nel.org, lorenzo.stoakes@...cle.com,
 Liam.Howlett@...cle.com, vbabka@...e.cz, rppt@...nel.org, surenb@...gle.com,
 mhocko@...e.com, axelrasmussen@...gle.com, yuanchu@...gle.com,
 weixugc@...gle.com, zhengqi.arch@...edance.com, shakeel.butt@...ux.dev,
 linux-mm@...ck.org, linux-kernel@...r.kernel.org, lujialin4@...wei.com,
 chenridong@...wei.com
Subject: Re: [RFC -next] memcg: Optimize creation performance when LRU_GEN is
 enabled



On 2025/11/27 17:04, Chen Ridong wrote:
> 
> 
> On 2025/11/27 1:15, Johannes Weiner wrote:
>> On Wed, Nov 19, 2025 at 08:37:22AM +0000, Chen Ridong wrote:
>>> From: Chen Ridong <chenridong@...wei.com>
>>>
>>> With LRU_GEN=y and LRU_GEN_ENABLED=n, a performance regression occurs
>>> when creating a large number of memory cgroups (memcgs):
>>>
>>> 	# time mkdir testcg_{1..10000}
>>>
>>> 	real	0m7.167s
>>> 	user	0m0.037s
>>> 	sys	0m6.773s
>>>
>>> 	# time mkdir testcg_{1..20000}
>>>
>>> 	real	0m27.158s
>>> 	user	0m0.079s
>>> 	sys	0m26.270s
>>>
>>> In contrast, with LRU_GEN=n, creation of the same number of memcgs
>>> performs better:
>>>
>>> 	# time mkdir testcg_{1..10000}
>>>
>>> 	real	0m3.386s
>>> 	user	0m0.044s
>>> 	sys	0m3.009s
>>>
>>> 	# time mkdir testcg_{1..20000}
>>>
>>> 	real	0m6.876s
>>> 	user	0m0.075s
>>> 	sys	0m6.121s
>>>
>>> The root cause is that lru_gen node onlining uses hlist_nulls_add_tail_rcu,
>>> which traverses the entire list to find the tail. This traversal scales
>>> with the number of memcgs, even when LRU_GEN is runtime-disabled.
>>
>> Can you please look into removing the memcg LRU instead?
>>
> 
> Thanks Johannes, this is indeed a promising approach.
> 
> The memcg LRU was originally designed exclusively for global reclaim scenarios. Before we move
> forward with its removal, I'd like to hear Yu's thoughts on this.
> 
> Hello Yu,
> 
> Do you have any opinions on removing the memcg LRU?
> 

Hello Johannes and Yu,

I've sent patches to remove the memcg LRU and replace it with mem_cgroup_iter.
I would appreciate it if you could take a look when you have time.

-- 
Best regards,
Ridong