From: Shakeel Butt <shakeelb@google.com>
To: Nico Pache <npache@redhat.com>
Cc: Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Rafael Aquini <aquini@redhat.com>,
Waiman Long <longman@redhat.com>
Subject: Re: [PATCH] vm_swappiness=0 should still try to avoid swapping anon memory
Date: Fri, 6 Aug 2021 22:23:48 -0700 [thread overview]
Message-ID: <CALvZod6Kv_eZcZeJOvypXe_XVzkvLDau7faiDQ2mrqV8kOqq3g@mail.gmail.com> (raw)
In-Reply-To: <91605888-e343-2712-c097-bcade4cb389d@redhat.com>
On Fri, Aug 6, 2021 at 6:37 PM Nico Pache <npache@redhat.com> wrote:
>
>
> On 8/6/21 9:00 PM, Shakeel Butt wrote:
[...]
> > If you are really seeing the said behavior then why will this fix it.
> > This is just about deactivating active anon LRU. I would rather look
> > at get_scan_count() to check why swappiness = 0 is still letting the
> > kernel to scan anon LRU. BTW in cgroup v1, the memcg can overwrite
> > their swappiness which will be preferred over system vm_swappiness.
> > Did you set system level swappiness or memcg one?
>
> This fixes the issue because shrink_list() uses the may_deactivate field
> to determine if it should shrink the active list.
First, the shrink_list() will not be called for anon LRU if get_scan_count()
has decided to not scan the anon LRU.
Second, I would like to get your attention to the following comment in
get_scan_count():
"Global reclaim will swap to prevent OOM even with no swappiness"
It seems like the behavior you are seeing is actually working as intended.
You may decide to change that behavior but you will need to motivate the
change.
next prev parent reply other threads:[~2021-08-07 5:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 23:17 [PATCH] vm_swappiness=0 should still try to avoid swapping anon memory Nico Pache
2021-08-07 1:00 ` Shakeel Butt
2021-08-07 1:37 ` Nico Pache
2021-08-07 5:23 ` Shakeel Butt [this message]
2021-08-09 11:49 ` Michal Hocko
2021-08-09 22:31 ` Nico Pache
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=CALvZod6Kv_eZcZeJOvypXe_XVzkvLDau7faiDQ2mrqV8kOqq3g@mail.gmail.com \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=npache@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).