linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: ying chen <yc1082463@gmail.com>
To: Shakeel Butt <shakeel.butt@linux.dev>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/vmscan: when the swappiness is set to 0, memory swapping should be prohibited during the global reclaim process
Date: Fri, 28 Feb 2025 10:48:48 +0800	[thread overview]
Message-ID: <CAN2Y7hxehoKP0UxPzuuVGv=Zjy2FtrAwgEuc7i07NJUc0ypZ5A@mail.gmail.com> (raw)
In-Reply-To: <5u6rwht2mdwi3t4x3r5gtelruihtvfak24ci32moh2v7z52a3g@qkr2jcjgh4dw>

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@linux.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@gmail.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?
>


  reply	other threads:[~2025-02-28  2:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 14:34 ying chen
2025-02-27 15:54 ` Joshua Hahn
2025-02-27 16:19   ` Johannes Weiner
2025-02-28  3:18     ` ying chen
2025-02-28  3:21     ` Yafang Shao
2025-02-28  3:16   ` ying chen
2025-02-27 19:12 ` Shakeel Butt
2025-02-28  2:48   ` ying chen [this message]
2025-03-03 12:07 ` Michal Hocko
  -- strict thread matches above, loose matches on Subject: below --
2025-02-27  7:51 ying chen

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='CAN2Y7hxehoKP0UxPzuuVGv=Zjy2FtrAwgEuc7i07NJUc0ypZ5A@mail.gmail.com' \
    --to=yc1082463@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox