From: Usama Arif <usama.arif@linux.dev>
To: Lance Yang <lance.yang@linux.dev>, akpm@linux-foundation.org
Cc: david@kernel.org, ljs@kernel.org, shakeel.butt@linux.dev,
mhocko@kernel.org, david@fromorbit.com, roman.gushchin@linux.dev,
muchun.song@linux.dev, qi.zheng@linux.dev, yosry.ahmed@linux.dev,
ziy@nvidia.com, liam@infradead.org, kas@kernel.org,
vbabka@kernel.org, ryncsn@gmail.com, zaslonko@linux.ibm.com,
gor@linux.ibm.com, wangkefeng.wang@huawei.com,
baolin.wang@linux.alibaba.com, baohua@kernel.org,
dev.jain@arm.com, npache@redhat.com, ryan.roberts@arm.com,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] mm/thp: clear deferred split shrinker bits when queues drain
Date: Tue, 2 Jun 2026 11:30:36 +0100 [thread overview]
Message-ID: <23946ec7-4728-4716-af18-29e303ac19e1@linux.dev> (raw)
In-Reply-To: <20260602043453.67597-1-lance.yang@linux.dev>
On 02/06/2026 05:34, Lance Yang wrote:
> From: Lance Yang <lance.yang@linux.dev>
>
> deferred_split_count() returns the raw list_lru count. When the per-memcg,
> per-node list is empty, that count is 0.
>
> That skips scanning, but it does not tell memcg reclaim that the shrinker
> is empty. shrink_slab_memcg() only clears the memcg shrinker bit when the
> count callback reports SHRINK_EMPTY.
>
> Return SHRINK_EMPTY for an empty deferred split list, so the bit can be
> cleared once the queue has drained.
>
> Signed-off-by: Lance Yang <lance.yang@linux.dev>
Same as slab, workingset and others.
Acked-by: Usama Arif <usama.arif@linux.dev>
next prev parent reply other threads:[~2026-06-02 10:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 4:34 [PATCH 1/1] mm/thp: clear deferred split shrinker bits when queues drain Lance Yang
2026-06-02 4:38 ` Lance Yang
2026-06-02 12:11 ` David Hildenbrand (Arm)
2026-06-02 12:47 ` Lance Yang
2026-06-02 17:33 ` David Hildenbrand (Arm)
2026-06-02 10:30 ` Usama Arif [this message]
2026-06-02 20:37 ` Andrew Morton
2026-06-03 2:00 ` Lance Yang
2026-06-03 8:02 ` David Hildenbrand (Arm)
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=23946ec7-4728-4716-af18-29e303ac19e1@linux.dev \
--to=usama.arif@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=cgroups@vger.kernel.org \
--cc=david@fromorbit.com \
--cc=david@kernel.org \
--cc=dev.jain@arm.com \
--cc=gor@linux.ibm.com \
--cc=kas@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=npache@redhat.com \
--cc=qi.zheng@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=ryncsn@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=vbabka@kernel.org \
--cc=wangkefeng.wang@huawei.com \
--cc=yosry.ahmed@linux.dev \
--cc=zaslonko@linux.ibm.com \
--cc=ziy@nvidia.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