From: Andrew Morton <akpm@linux-foundation.org>
To: "Shakeel Butt" <shakeelb@google.com>,
" Michal Koutný " <mkoutny@suse.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Hocko" <mhocko@kernel.org>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Ivan Babrou" <ivan@cloudflare.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
"Daniel Dao" <dqminh@cloudflare.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] memcg: async flush memcg stats from perf sensitive codepaths
Date: Fri, 25 Feb 2022 17:20:20 -0800 [thread overview]
Message-ID: <20220225172020.b3e59e11a0a3dd15e0d34141@linux-foundation.org> (raw)
In-Reply-To: <20220225165842.561d3a475310aeab86a2d653@linux-foundation.org>
On Fri, 25 Feb 2022 16:58:42 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
> On Fri, 25 Feb 2022 16:24:12 -0800 Shakeel Butt <shakeelb@google.com> wrote:
>
> > Daniel Dao has reported [1] a regression on workloads that may trigger
> > a lot of refaults (anon and file). The underlying issue is that flushing
> > rstat is expensive. Although rstat flush are batched with (nr_cpus *
> > MEMCG_BATCH) stat updates, it seems like there are workloads which
> > genuinely do stat updates larger than batch value within short amount of
> > time. Since the rstat flush can happen in the performance critical
> > codepaths like page faults, such workload can suffer greatly.
> >
> > The easiest fix for now is for performance critical codepaths trigger
> > the rstat flush asynchronously. This patch converts the refault codepath
> > to use async rstat flush. In addition, this patch has premptively
> > converted mem_cgroup_wb_stats and shrink_node to also use the async
> > rstat flush as they may also similar performance regressions.
>
> Gee we do this trick a lot and gee I don't like it :(
>
> a) if we're doing too much work then we're doing too much work.
> Punting that work over to a different CPU or thread doesn't alter
> that - it in fact adds more work.
>
> b) there's an assumption here that the flusher is able to keep up
> with the producer. What happens if that isn't the case? Do we
> simply wind up the deferred items until the system goes oom?
>
> What happens if there's a producer running on each CPU? Can the
> flushers keep up?
>
> Pathologically, what happens if the producer is running
> task_is_realtime() on a single-CPU system? Or if there's a
> task_is_realtime() producer running on every CPU? The flusher never
> gets to run and we're dead?
Not some theoretical thing, btw. See how __read_swap_cache_async()
just got its sins exposed by real-time tasks:
https://lkml.kernel.org/r/20220221111749.1928222-1-cgel.zte@gmail.com
next prev parent reply other threads:[~2022-02-26 1:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 0:24 Shakeel Butt
2022-02-26 0:58 ` Andrew Morton
2022-02-26 1:20 ` Andrew Morton [this message]
2022-02-26 1:42 ` Shakeel Butt
2022-02-28 18:46 ` Michal Koutný
2022-02-28 22:46 ` Shakeel Butt
2022-02-26 2:32 ` kernel test robot
2022-02-26 12:43 ` kernel test robot
2022-03-01 9:05 ` Michal Hocko
2022-03-01 17:21 ` Shakeel Butt
2022-03-01 17:57 ` Michal Koutný
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=20220225172020.b3e59e11a0a3dd15e0d34141@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=dqminh@cloudflare.com \
--cc=hannes@cmpxchg.org \
--cc=ivan@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=stable@vger.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