From: Jakub Kicinski <kuba@kernel.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
kernel-team@fb.com, tj@kernel.org, hannes@cmpxchg.org,
chris@chrisdown.name, cgroups@vger.kernel.org
Subject: Re: [PATCH 3/3] mm: automatically penalize tasks with high swap use
Date: Fri, 17 Apr 2020 16:22:48 -0700 [thread overview]
Message-ID: <20200417162248.415ff51e@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <20200417073716.GG26707@dhcp22.suse.cz>
On Fri, 17 Apr 2020 09:37:16 +0200 Michal Hocko wrote:
> On Thu 16-04-20 18:06:17, Jakub Kicinski wrote:
> > Add a memory.swap.high knob, which functions in a similar way
> > to memory.high, but with a less steep slope.
>
> This really begs for more details. What does "similar way to
> memory.high" mean? Because my first thought would be that the swap usage
> will be throttled and kept at the swap.high level. From a quick look at
> the patch you only do throttling. There is no swap space reclaim to keep
> the usage at the level. So unless I am missing something this is very
> confusing and it doesn't really fit into high limit semantic.
The new knob does influence mem_cgroup_swap_full(), but you're right,
the analogy is not strong enough, I'll rephrase.
> This changelog also doesn't describe any usecase.
Will do.
next prev parent reply other threads:[~2020-04-17 23:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 1:06 [PATCH 0/3] memcg: Slow down swap allocation as the available space gets depleted Jakub Kicinski
2020-04-17 1:06 ` [PATCH 1/3] mm: prepare for swap over-high accounting and penalty calculation Jakub Kicinski
2020-04-17 1:06 ` [PATCH 2/3] mm: move penalty delay clamping out of calculate_high_delay() Jakub Kicinski
2020-04-17 1:06 ` [PATCH 3/3] mm: automatically penalize tasks with high swap use Jakub Kicinski
2020-04-17 7:37 ` Michal Hocko
2020-04-17 23:22 ` Jakub Kicinski [this message]
2020-04-17 16:11 ` [PATCH 0/3] memcg: Slow down swap allocation as the available space gets depleted Shakeel Butt
2020-04-17 16:23 ` Tejun Heo
2020-04-17 17:18 ` Shakeel Butt
2020-04-17 17:36 ` Tejun Heo
2020-04-17 17:51 ` Shakeel Butt
2020-04-17 19:35 ` Tejun Heo
2020-04-17 21:51 ` Shakeel Butt
2020-04-17 22:59 ` Tejun Heo
2020-04-20 16:12 ` Shakeel Butt
2020-04-20 16:47 ` Tejun Heo
2020-04-20 17:03 ` Michal Hocko
2020-04-20 17:06 ` Tejun Heo
2020-04-21 11:06 ` Michal Hocko
2020-04-21 14:27 ` Johannes Weiner
2020-04-21 16:11 ` Michal Hocko
2020-04-21 16:56 ` Johannes Weiner
2020-04-22 13:26 ` Michal Hocko
2020-04-22 14:15 ` Johannes Weiner
2020-04-22 15:43 ` Michal Hocko
2020-04-22 17:13 ` Johannes Weiner
2020-04-22 18:49 ` Michal Hocko
2020-04-23 15:00 ` Johannes Weiner
2020-04-24 15:05 ` Michal Hocko
2020-04-28 14:24 ` Johannes Weiner
2020-04-29 9:55 ` Michal Hocko
2020-04-21 19:09 ` Shakeel Butt
2020-04-21 21:59 ` Johannes Weiner
2020-04-21 22:39 ` Shakeel Butt
2020-04-21 15:20 ` Tejun Heo
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=20200417162248.415ff51e@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=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