From: Alexey Avramov <hakavlad@inbox.lv>
To: Nico Pache <npache@redhat.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, hannes@cmpxchg.org,
aquini@redhat.com, shakeelb@google.com, llong@redhat.com
Subject: Re: [PATCH v2] vm_swappiness=0 should still try to avoid swapping anon memory
Date: Sat, 7 Aug 2021 15:14:24 +0900 [thread overview]
Message-ID: <20210807151424.76b4ee3a@mail.inbox.lv> (raw)
In-Reply-To: <20210807022129.8842-1-npache@redhat.com>
>vm_swappiness=0 should still try to avoid swapping anon memory
Swapping with swappiness=0 depends on vm.watermark_scale_factor.
Decrease vm.watermark_scale_factor to avoid swapping and get OOM,
and increase vm.watermark_scale_factor to get successful swapping
even with swappiness=0.
Maybe I misunderstood you and you are solving some new problem?
next prev parent reply other threads:[~2021-08-07 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 2:21 [PATCH v2] vm_swappiness=0 should still try to avoid swapping anon memory Nico Pache
2021-08-07 6:14 ` Alexey Avramov [this message]
2021-08-09 21:19 ` 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=20210807151424.76b4ee3a@mail.inbox.lv \
--to=hakavlad@inbox.lv \
--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=llong@redhat.com \
--cc=npache@redhat.com \
--cc=shakeelb@google.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).