From: Usama Arif <usama.arif@linux.dev>
To: Qi Zheng <qi.zheng@linux.dev>,
brauner@kernel.org, jack@suse.cz, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
linux-mm@kvack.org
Cc: hughd@google.com, boris@bur.io, clm@fb.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, cem@kernel.org,
linux-xfs@vger.kernel.org, shakeel.butt@linux.dev,
hannes@cmpxchg.org, riel@surriel.com, kernel-team@meta.com
Subject: Re: [PATCH] fs/super: skip non-memcg-aware nr_cached_objects in memcg slab shrink
Date: Mon, 13 Jul 2026 16:34:52 +0100 [thread overview]
Message-ID: <a0c0a578-9334-4540-b469-4c368d07953e@linux.dev> (raw)
In-Reply-To: <4752c658-7b61-4636-ab5b-bd172e11a42c@linux.dev>
On 13/07/2026 14:12, Qi Zheng wrote:
> Hi Usama,
>
> On 6/9/26 8:30 PM, Usama Arif wrote:
>> The super_block shrinker is registered with SHRINKER_MEMCG_AWARE because its
>> dentry and inode LRUs are memcg-aware (via list_lru). But the optional
>> ->nr_cached_objects() hooks that the shrinker also drives are not memcg-aware:
>> btrfs extent maps and xfs inode reclaim operate on filesystem-global
>> state, and shmem's unused-huge shrinker walks a per-superblock shrinklist.
>> None of them filter by sc->memcg.
>
> This makes sense for now, but how should we handle this if these
> shrinkers are made memcg-aware in the future?
>
> I've recently been working on making the shmem huge shrinker
> memcg-aware, but noticed my changes broke after rebasing onto the latest
> tree, which led me to this patch.
>
> As for the shmem huge shrinker, I can work around this limitation by
> making it a separate shrinker. But this feels more like an overall
> design decision, effectively meaning that all nr_cached_objects are
> precluded from being memcg-aware.
>
> Thanks,
> Qi
>
Hi Qi,
Thanks for raising this. I think the alternative is what I mentioned in
https://lore.kernel.org/all/cfdb8620-ea55-4226-98bf-d006820e6270@linux.dev/
move this down to the fs own callbacks instead of here. Would that
be better?
Thanks,
Usama
next prev parent reply other threads:[~2026-07-13 16:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 12:30 [PATCH] fs/super: skip non-memcg-aware nr_cached_objects in memcg slab shrink Usama Arif
2026-06-09 12:52 ` Jan Kara
2026-06-09 13:38 ` Usama Arif
2026-06-23 10:14 ` Christian Brauner
2026-06-23 18:08 ` Shakeel Butt
2026-06-24 15:18 ` Usama Arif
2026-07-13 13:12 ` Qi Zheng
2026-07-13 15:34 ` Usama Arif [this message]
2026-07-14 2:09 ` Qi Zheng
2026-07-14 10:17 ` Usama Arif
2026-07-14 10:52 ` Qi Zheng
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=a0c0a578-9334-4540-b469-4c368d07953e@linux.dev \
--to=usama.arif@linux.dev \
--cc=boris@bur.io \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=kernel-team@meta.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=qi.zheng@linux.dev \
--cc=riel@surriel.com \
--cc=shakeel.butt@linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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