From: Qi Zheng <qi.zheng@linux.dev>
To: "Michal Koutný" <mkoutny@suse.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Dave Chinner" <david@fromorbit.com>,
"Qi Zheng" <zhengqi.arch@bytedance.com>,
"Roman Gushchin" <roman.gushchin@linux.dev>,
"Muchun Song" <muchun.song@linux.dev>
Cc: Jan Kara <jack@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Do not allocate shrinker info with cgroup.memory=nokmem
Date: Thu, 26 Feb 2026 15:16:13 +0800 [thread overview]
Message-ID: <835ed9a0-da93-4e34-b967-f91954a329b8@linux.dev> (raw)
In-Reply-To: <20260225-cgroup-ml-nokmem-shrinker-v1-1-d703899bdda4@suse.com>
On 2/26/26 2:38 AM, Michal Koutný wrote:
> There'd be no work for memcg-aware shrinkers when kernel memory is not
> accounted per cgroup, so we can skip allocating per memcg shrinker data.
> This saves some memory, avoids holding shrinker_mutex with O(nr_memcgs)
> and saves work in shrink_slab_memcg().
>
> Then there are SHRINKER_NONSLAB shrinkers which handle non-kernel memory
> so nokmem should not disable their per-memcg behavior. Such shrinkers
> (e.g. deferred_split_shrinker) still need access to per-memcg data (see
> also commit 0a432dcbeb32e ("mm: shrinker: make shrinker not depend on
> memcg kmem")).
>
> The savings with this patch come on container hosts that create many
> superblocks (each with own shrinker) but tracking and processing
> per-memcg data is pointless with nokmem (shrink_slab_memcg() is
> partially guarded with !memcg_kmem_online already).
>
> The patch uses "boottime" predicate mem_cgroup_kmem_disabled() (not
> memcg_kmem_online()) to avoid mistakenly un-MEMCG_AWARE-ing shrinkers
> registered before first non-root memcg is mkdir'd.
>
> Signed-off-by: Michal Koutný <mkoutny@suse.com>
> ---
> mm/shrinker.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/shrinker.c b/mm/shrinker.c
> index 4a93fd433689a..7d7302619b7f7 100644
> --- a/mm/shrinker.c
> +++ b/mm/shrinker.c
> @@ -219,6 +219,8 @@ static int shrinker_memcg_alloc(struct shrinker *shrinker)
>
> if (mem_cgroup_disabled())
> return -ENOSYS;
> + if (mem_cgroup_kmem_disabled() && !(shrinker->flags & SHRINKER_NONSLAB))
> + return -ENOSYS;
Make sense, and can you help update the following comment in
shrinker_alloc() as well:
/*
* The nr_deferred is available on per memcg level for memcg aware
* shrinkers, so only allocate nr_deferred in the following cases:
* - non-memcg-aware shrinkers
* - !CONFIG_MEMCG
* - memcg is disabled by kernel command line
*/
Otherwise:
Acked-by: Qi Zheng <zhengqi.arch@bytedance.com>
Thanks,
Qi
>
> mutex_lock(&shrinker_mutex);
> id = idr_alloc(&shrinker_idr, shrinker, 0, 0, GFP_KERNEL);
>
> ---
> base-commit: cd2e103d57e5615f9bb027d772f93b9efd567224
> change-id: 20260225-cgroup-ml-nokmem-shrinker-7da42fbcf8f2
>
> Best regards,
next prev parent reply other threads:[~2026-02-26 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 18:38 Michal Koutný
2026-02-26 0:25 ` Roman Gushchin
2026-02-26 7:16 ` Qi Zheng [this message]
2026-02-26 7:19 ` Muchun Song
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=835ed9a0-da93-4e34-b967-f91954a329b8@linux.dev \
--to=qi.zheng@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mkoutny@suse.com \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=zhengqi.arch@bytedance.com \
/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