From: Waiman Long <llong@redhat.com>
To: Shakeel Butt <shakeel.butt@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Muchun Song <muchun.song@linux.dev>,
Yosry Ahmed <yosry.ahmed@linux.dev>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org,
Meta kernel team <kernel-team@meta.com>
Subject: Re: [PATCH] memcg: optimize memcg_rstat_updated
Date: Wed, 9 Apr 2025 21:20:34 -0400 [thread overview]
Message-ID: <2f9d478d-3359-40c8-8607-be906eaeea04@redhat.com> (raw)
In-Reply-To: <20250409234908.940121-1-shakeel.butt@linux.dev>
[-- Attachment #1: Type: text/plain, Size: 2159 bytes --]
On 4/9/25 7:49 PM, Shakeel Butt wrote:
> Currently the kernel maintains the stats updates per-memcg which is
> needed to implement stats flushing threshold. On the update side, the
> update is added to the per-cpu per-memcg update of the given memcg and
> all of its ancestors. However when the given memcg has passed the
> flushing threshold, all of its ancestors should have passed the
> threshold as well. There is no need to traverse up the memcg tree to
> maintain the stats updates.
>
> Perf profile collected from our fleet shows that memcg_rstat_updated is
> one of the most expensive memcg function i.e. a lot of cumulative CPU
> is being spent on it. So, even small micro optimizations matter a lot.
>
> Signed-off-by: Shakeel Butt<shakeel.butt@linux.dev>
> ---
> mm/memcontrol.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 421740f1bcdc..ea3e40e589df 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -585,18 +585,20 @@ static inline void memcg_rstat_updated(struct mem_cgroup *memcg, int val)
> cgroup_rstat_updated(memcg->css.cgroup, cpu);
> statc = this_cpu_ptr(memcg->vmstats_percpu);
> for (; statc; statc = statc->parent) {
> + /*
> + * If @memcg is already flushable then all its ancestors are
> + * flushable as well and also there is no need to increase
> + * stats_updates.
> + */
> + if (!memcg_vmstats_needs_flush(statc->vmstats))
> + break;
> +
Do you mean "if (memcg_vmstats_needs_flush(statc->vmstats))"?
Cheers, Longman
> stats_updates = READ_ONCE(statc->stats_updates) + abs(val);
> WRITE_ONCE(statc->stats_updates, stats_updates);
> if (stats_updates < MEMCG_CHARGE_BATCH)
> continue;
>
> - /*
> - * If @memcg is already flush-able, increasing stats_updates is
> - * redundant. Avoid the overhead of the atomic update.
> - */
> - if (!memcg_vmstats_needs_flush(statc->vmstats))
> - atomic64_add(stats_updates,
> - &statc->vmstats->stats_updates);
> + atomic64_add(stats_updates, &statc->vmstats->stats_updates);
> WRITE_ONCE(statc->stats_updates, 0);
> }
> }
[-- Attachment #2: Type: text/html, Size: 2796 bytes --]
next prev parent reply other threads:[~2025-04-10 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 23:49 Shakeel Butt
2025-04-10 1:20 ` Waiman Long [this message]
2025-04-10 1:49 ` Shakeel Butt
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=2f9d478d-3359-40c8-8607-be906eaeea04@redhat.com \
--to=llong@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=yosry.ahmed@linux.dev \
/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