From: Jakub Kicinski <kuba@kernel.org>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, kernel-team@fb.com, tj@kernel.org,
hannes@cmpxchg.org, chris@chrisdown.name,
cgroups@vger.kernel.org, shakeelb@google.com, mhocko@kernel.org
Subject: Re: [PATCH mm v5 0/4] memcg: Slow down swap allocation as the available space gets depleted
Date: Wed, 20 May 2020 17:22:06 -0700 [thread overview]
Message-ID: <20200520172206.4e55b66f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200521002010.3962544-1-kuba@kernel.org>
On Wed, 20 May 2020 17:20:06 -0700 Jakub Kicinski wrote:
> Tejun describes the problem as follows:
>
> When swap runs out, there's an abrupt change in system behavior -
> the anonymous memory suddenly becomes unmanageable which readily
> breaks any sort of memory isolation and can bring down the whole
> system. To avoid that, oomd [1] monitors free swap space and triggers
> kills when it drops below the specific threshold (e.g. 15%).
>
> While this works, it's far from ideal:
> - Depending on IO performance and total swap size, a given
> headroom might not be enough or too much.
> - oomd has to monitor swap depletion in addition to the usual
> pressure metrics and it currently doesn't consider memory.swap.max.
>
> Solve this by adapting parts of the approach that memory.high uses -
> slow down allocation as the resource gets depleted turning the
> depletion behavior from abrupt cliff one to gradual degradation
> observable through memory pressure metric.
>
> [1] https://github.com/facebookincubator/oomd
>
> v4: https://lore.kernel.org/linux-mm/20200519171938.3569605-1-kuba@kernel.org/
> v3: https://lore.kernel.org/linux-mm/20200515202027.3217470-1-kuba@kernel.org/
> v2: https://lore.kernel.org/linux-mm/20200511225516.2431921-1-kuba@kernel.org/
> v1: https://lore.kernel.org/linux-mm/20200417010617.927266-1-kuba@kernel.org/
Ah, damn, I forgot to add Shakeel's review tags, let me resend.
prev parent reply other threads:[~2020-05-21 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 0:20 Jakub Kicinski
2020-05-21 0:20 ` [PATCH mm v5 1/4] mm: prepare for swap over-high accounting and penalty calculation Jakub Kicinski
2020-05-21 0:20 ` [PATCH mm v5 2/4] mm: move penalty delay clamping out of calculate_high_delay() Jakub Kicinski
2020-05-21 0:20 ` [PATCH mm v5 3/4] mm: move cgroup high memory limit setting into struct page_counter Jakub Kicinski
2020-05-21 0:20 ` [PATCH mm v5 4/4] mm: automatically penalize tasks with high swap use Jakub Kicinski
2020-05-21 0:22 ` Jakub Kicinski [this message]
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=20200520172206.4e55b66f@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
/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