From: Haifeng Xu <haifeng.xu@shopee.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: david@fromorbit.com, roman.gushchin@linux.dev,
hannes@cmpxchg.org, mhocko@kernel.org, shakeel.butt@linux.dev,
zhengqi.arch@bytedance.com, muchun.song@linux.dev,
usama.arif@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 3/4] mm: shrinker: optimize the allocation of shrinker_info when setting cgroup_memory_nokmem
Date: Thu, 12 Mar 2026 12:16:15 +0800 [thread overview]
Message-ID: <26ddcfcf-cdde-436f-860a-4cdf574e51bc@shopee.com> (raw)
In-Reply-To: <20260311141928.b4291eae43f99a2f6912cd2d@linux-foundation.org>
On 2026/3/12 05:19, Andrew Morton wrote:
> On Wed, 11 Mar 2026 11:02:34 +0800 Haifeng Xu <haifeng.xu@shopee.com> wrote:
>
>> When kmem is disabled, memcg slab shrink only call non-slab shrinkers,
>> so just allocates shrinker info for non-slab shrinkers to non-root memcgs.
>
> What happens if memcg kmem is enabled later on?
cgroup_memory_nokmem is a boot parameter. If memcg kmem is enabled, all things
keep same as before, root and non-root memcgs allocate id from shrinker_idr.
next prev parent reply other threads:[~2026-03-12 4:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 3:02 [PATCH V3 0/4] record non-slab shrinkers for non-root memcgs when kmem is disabled Haifeng Xu
2026-03-11 3:02 ` [PATCH V3 1/4] mm: shrinker: add one more parameter in shrinker_id() Haifeng Xu
2026-03-11 3:02 ` [PATCH V3 2/4] mm: shrinker: move shrinker_id() code block below memcg_kmem_online() Haifeng Xu
2026-03-11 3:02 ` [PATCH V3 3/4] mm: shrinker: optimize the allocation of shrinker_info when setting cgroup_memory_nokmem Haifeng Xu
2026-03-11 21:19 ` Andrew Morton
2026-03-12 4:16 ` Haifeng Xu [this message]
2026-03-11 3:02 ` [PATCH V3 4/4] mm: shrinker: remove unnecessary check in shrink_slab_memcg() Haifeng Xu
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=26ddcfcf-cdde-436f-860a-4cdf574e51bc@shopee.com \
--to=haifeng.xu@shopee.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hannes@cmpxchg.org \
--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=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