linux-kernel - Re: [PATCH] mm/vmscan: when the swappiness is set to 0, memory swapping should be prohibited during the global reclaim process

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: <CAN2Y7hxehoKP0UxPzuuVGv=Zjy2FtrAwgEuc7i07NJUc0ypZ5A@mail.gmail.com>
Date: Fri, 28 Feb 2025 10:48:48 +0800
From: ying chen <yc1082463@...il.com>
To: Shakeel Butt <shakeel.butt@...ux.dev>
Cc: akpm@...ux-foundation.org, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/vmscan: when the swappiness is set to 0, memory
 swapping should be prohibited during the global reclaim process

Yes, I'm still using memcg-v1. But it's too expensive for us to
migrate the production environment to memcg-v2.

On Fri, Feb 28, 2025 at 3:12 AM Shakeel Butt <shakeel.butt@...ux.dev> wrote:
>
> On Thu, Feb 27, 2025 at 10:34:51PM +0800, ying chen wrote:
> > When we use zram as swap disks, global reclaim may cause the memory in some
> > cgroups with memory.swappiness set to 0 to be swapped into zram. This memory
> > won't be swapped back immediately after the free memory increases. Instead,
> > it will continue to occupy the zram space, which may result in no available
> > zram space for the cgroups with swapping enabled. Therefore, I think that
> > when the vm.swappiness is set to 0, global reclaim should also refrain
> > from memory swapping, just like these cgroups.
> >
> > Signed-off-by: yc1082463 <yc1082463@...il.com>
>
> It seems like you are still on memcg-v1. What is stopping you to move to
> memcg-v2 and use memory.swap.max = 0?
>