From: Shakeel Butt <shakeel.butt@linux.dev>
To: Dave Chinner <dgc@kernel.org>
Cc: Usama Arif <usama.arif@linux.dev>,
brauner@kernel.org, qi.zheng@linux.dev, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
linux-mm@kvack.org, 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, hannes@cmpxchg.org, riel@surriel.com,
kernel-team@meta.com
Subject: Re: [PATCH] fs: push nr_cached_objects memcg gating into individual filesystems
Date: Tue, 14 Jul 2026 15:54:47 -0700 [thread overview]
Message-ID: <ala6pd9jmPccGjgC@linux.dev> (raw)
In-Reply-To: <ala2rDHrFDjql3Qg@dread>
On Wed, Jul 15, 2026 at 08:22:36AM +1000, Dave Chinner wrote:
> On Tue, Jul 14, 2026 at 03:14:54AM -0700, Usama Arif wrote:
> > Commit 0baad6f9b997 ("fs/super: skip non-memcg-aware nr_cached_objects
> > in memcg slab shrink") added a check in fs/super.c that skips the
> > ->nr_cached_objects() hook whenever the shrinker is invoked for a
> > non-root memcg, because none of the current implementations (btrfs,
> > xfs, shmem huge) honour sc->memcg.
>
> I don't see that commit in an upstream tree. I'm guessing I wasn't
> cc'd on it, either, because I don't recall seeing that as a patch,
> either.
https://lore.kernel.org/all/20260609123047.1948242-1-usama.arif@linux.dev/
next prev parent reply other threads:[~2026-07-14 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 10:14 [PATCH] fs: push nr_cached_objects memcg gating into individual filesystems Usama Arif
2026-07-14 10:56 ` Qi Zheng
2026-07-14 15:20 ` Jan Kara
2026-07-14 19:41 ` Shakeel Butt
2026-07-14 22:22 ` Dave Chinner
2026-07-14 22:54 ` Shakeel Butt [this message]
2026-07-15 10:26 ` Usama Arif
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=ala6pd9jmPccGjgC@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=boris@bur.io \
--cc=brauner@kernel.org \
--cc=cem@kernel.org \
--cc=clm@fb.com \
--cc=dgc@kernel.org \
--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=usama.arif@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