From: Johannes Weiner <hannes@cmpxchg.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
kernel-team@fb.com, tj@kernel.org, chris@chrisdown.name,
cgroups@vger.kernel.org, shakeelb@google.com, mhocko@kernel.org
Subject: Re: [PATCH mm v5 RESEND 4/4] mm: automatically penalize tasks with high swap use
Date: Wed, 27 May 2020 11:51:45 -0400 [thread overview]
Message-ID: <20200527155145.GA42293@cmpxchg.org> (raw)
In-Reply-To: <20200526131157.79c17940@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
On Tue, May 26, 2020 at 01:11:57PM -0700, Jakub Kicinski wrote:
> On Tue, 26 May 2020 11:33:09 -0400 Johannes Weiner wrote:
> > On Wed, May 20, 2020 at 05:24:11PM -0700, Jakub Kicinski wrote:
> > > + penalty_jiffies += calculate_high_delay(memcg, nr_pages,
> > > + swap_find_max_overage(memcg));
> > > +
> > > /*
> > > * Clamp the max delay per usermode return so as to still keep the
> > > * application moving forwards and also permit diagnostics, albeit
> > > @@ -2585,12 +2608,25 @@ static int try_charge(struct mem_cgroup *memcg, gfp_t gfp_mask,
> > > * reclaim, the cost of mismatch is negligible.
> > > */
> > > do {
> > > - if (page_counter_is_above_high(&memcg->memory)) {
> > > - /* Don't bother a random interrupted task */
> > > - if (in_interrupt()) {
> > > + bool mem_high, swap_high;
> > > +
> > > + mem_high = page_counter_is_above_high(&memcg->memory);
> > > + swap_high = page_counter_is_above_high(&memcg->swap);
> >
> > Please open-code these checks instead - we don't really do getters and
> > predicates for these, and only have the setters because they are more
> > complicated operations.
>
> I added this helper because the calculation doesn't fit into 80 chars.
>
> In particular reclaim_high will need a temporary variable or IMHO
> questionable line split.
>
> static void reclaim_high(struct mem_cgroup *memcg,
> unsigned int nr_pages,
> gfp_t gfp_mask)
> {
> do {
> if (!page_counter_is_above_high(&memcg->memory))
> continue;
> memcg_memory_event(memcg, MEMCG_HIGH);
> try_to_free_mem_cgroup_pages(memcg, nr_pages, gfp_mask, true);
> } while ((memcg = parent_mem_cgroup(memcg)) &&
> !mem_cgroup_is_root(memcg));
> }
>
> What's your preference? Mine is a helper, but I'm probably not
> sensitive enough to the ontology here :)
if (page_counter_read(&memcg->memory) <
READ_ONCE(memcg->memory.high))
continue;
should work fine. It's the same formatting in mem_cgroup_swap_full():
if (page_counter_read(&memcg->swap) * 2 >=
READ_ONCE(memcg->swap.max))
prev parent reply other threads:[~2020-05-27 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 0:24 [PATCH mm v5 RESEND 0/4] memcg: Slow down swap allocation as the available space gets depleted Jakub Kicinski
2020-05-21 0:24 ` [PATCH mm v5 RESEND 1/4] mm: prepare for swap over-high accounting and penalty calculation Jakub Kicinski
2020-05-26 14:35 ` Johannes Weiner
2020-05-21 0:24 ` [PATCH mm v5 RESEND 2/4] mm: move penalty delay clamping out of calculate_high_delay() Jakub Kicinski
2020-05-26 14:36 ` Johannes Weiner
2020-05-21 0:24 ` [PATCH mm v5 RESEND 3/4] mm: move cgroup high memory limit setting into struct page_counter Jakub Kicinski
2020-05-26 14:42 ` Johannes Weiner
2020-05-21 0:24 ` [PATCH mm v5 RESEND 4/4] mm: automatically penalize tasks with high swap use Jakub Kicinski
2020-05-26 15:33 ` Johannes Weiner
2020-05-26 20:11 ` Jakub Kicinski
2020-05-27 15:51 ` Johannes Weiner [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=20200527155145.GA42293@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=chris@chrisdown.name \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).