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
| ||
|
Date: Sun, 22 May 2022 14:49:36 +0800 From: Muchun Song <songmuchun@...edance.com> To: Vasily Averin <vvs@...nvz.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, kernel@...nvz.org, LKML <linux-kernel@...r.kernel.org>, Linux Memory Management List <linux-mm@...ck.org>, Shakeel Butt <shakeelb@...gle.com>, Roman Gushchin <roman.gushchin@...ux.dev>, Michal Koutný <mkoutny@...e.com>, Vlastimil Babka <vbabka@...e.cz>, Michal Hocko <mhocko@...e.com>, Cgroups <cgroups@...r.kernel.org> Subject: Re: [PATCH mm v2 8/9] memcg: enable accounting for allocations in alloc_fair_sched_group On Sun, May 22, 2022 at 12:39 AM Vasily Averin <vvs@...nvz.org> wrote: > > Creating of each new cpu cgroup allocates two 512-bytes kernel objects > per CPU. This is especially important for cgroups shared parent memory > cgroup. In this scenario, on nodes with multiple processors, these > allocations become one of the main memory consumers. > > Memory allocated during new cpu cgroup creation: > common part: ~11Kb + 318 bytes percpu > cpu cgroup: ~2.5Kb + 1036 bytes percpu > > Accounting for this memory helps to avoid misuse inside memcg-limited > contianers. > > Signed-off-by: Vasily Averin <vvs@...nvz.org> Reviewed-by: Muchun Song <songmuchun@...edance.com>
Powered by blists - more mailing lists