The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Qi Zheng <qi.zheng@linux.dev>
To: Andrew Morton <akpm@linux-foundation.org>, brauner@kernel.org
Cc: hughd@google.com, baolin.wang@linux.alibaba.com,
	usama.arif@linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org,
	Qi Zheng <zhengqi.arch@bytedance.com>,
	Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] mm: shmem: make unused huge shrinker memcg aware
Date: Thu, 16 Jul 2026 10:20:14 +0800	[thread overview]
Message-ID: <64be6bbf-4e9f-4cd9-bfd5-24ac06286f1c@linux.dev> (raw)
In-Reply-To: <20260715124030.feb2d407e5e5ae28a39674a3@linux-foundation.org>



On 7/16/26 3:40 AM, Andrew Morton wrote:
> On Wed, 15 Jul 2026 14:49:28 +0800 Qi Zheng <qi.zheng@linux.dev> wrote:
> 
>>>
>>>> This patch is based on next-20260701 because it doesn't include this patch:
>>>>
>>>> https://lore.kernel.org/all/20260609123047.1948242-1-usama.arif@linux.dev/
>>>>
>>>> Later on, Usama will consider moving this restriction down into the fs callback.
>>>
>>> I'm not understanding.  Was Usama's above patch ever included in
>>> anything?
>>
>> It's included in linux-next, e.g. next-20260710.
> 
> Oh, OK, it came in via Christian's vfs.git tree.
> 
> 0baad6f9b997 ("fs/super: skip non-memcg-aware nr_cached_objects in memcg slab shrink")
> 
> Should we be asking Christian to make some alteration here?

I saw Usama posted an alternative (now at v2) and got Reviewed-bys:

https://lore.kernel.org/all/20260715103516.2410175-1-usama.arif@linux.dev/

Hi Christian, do you have plans to merge this into the vfs.git tree
recently?

Thanks,
Qi


  reply	other threads:[~2026-07-16  2:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14  3:19 [PATCH] mm: shmem: make unused huge shrinker memcg aware Qi Zheng
2026-07-15  4:32 ` Andrew Morton
2026-07-15  6:49   ` Qi Zheng
2026-07-15 19:40     ` Andrew Morton
2026-07-16  2:20       ` Qi Zheng [this message]
2026-07-15  9:37 ` Baolin Wang
2026-07-15  9:55   ` 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=64be6bbf-4e9f-4cd9-bfd5-24ac06286f1c@linux.dev \
    --to=qi.zheng@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=brauner@kernel.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=usama.arif@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