Linux cgroups development
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <ljs@kernel.org>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Michal Hocko <mhocko@kernel.org>,
	Dave Chinner <david@fromorbit.com>,
	Roman Gushchin <roman.gushchin@linux.dev>,
	Muchun Song <muchun.song@linux.dev>,
	Qi Zheng <qi.zheng@linux.dev>,
	Yosry Ahmed <yosry.ahmed@linux.dev>, Zi Yan <ziy@nvidia.com>,
	"Liam R . Howlett" <liam@infradead.org>,
	Usama Arif <usama.arif@linux.dev>,
	Kiryl Shutsemau <kas@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	Kairui Song <ryncsn@gmail.com>,
	Mikhail Zaslonko <zaslonko@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Barry Song <baohua@kernel.org>, Dev Jain <dev.jain@arm.com>,
	Lance Yang <lance.yang@linux.dev>, Nico Pache <npache@redhat.com>,
	Ryan Roberts <ryan.roberts@arm.com>,
	cgroups@vger.kernel.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 9/9] mm: switch deferred split shrinker to list_lru
Date: Sat, 20 Jun 2026 07:39:16 +0000	[thread overview]
Message-ID: <20260620073916.ico5v2kji4skpf5m@master> (raw)
In-Reply-To: <20260527204757.2544958-10-hannes@cmpxchg.org>

On Wed, May 27, 2026 at 04:45:16PM -0400, Johannes Weiner wrote:
[...]
>@@ -3890,34 +3804,43 @@ static int __folio_freeze_and_split_unmapped(struct folio *folio, unsigned int n
> 	struct folio *end_folio = folio_next(folio);
> 	struct folio *new_folio, *next;
> 	int old_order = folio_order(folio);
>+	struct list_lru_one *lru;
>+	bool dequeue_deferred;
> 	int ret = 0;
>-	struct deferred_split *ds_queue;
> 
> 	VM_WARN_ON_ONCE(!mapping && end);
>-	/* Prevent deferred_split_scan() touching ->_refcount */
>-	ds_queue = folio_split_queue_lock(folio);
>+	/*
>+	 * If this folio can be on the deferred split queue, lock out
>+	 * the shrinker before freezing the ref. If the shrinker sees
>+	 * a 0-ref folio, it assumes it beat folio_put() to the list
>+	 * lock and must clean up the LRU state - the same dequeue we
>+	 * will do below as part of the split.
>+	 */
>+	dequeue_deferred = folio_test_anon(folio) && old_order > 1;

Looking at __folio_remove_rmap(), we check !folio_is_device_private() before
deferred_split_folio(). __folio_freeze_and_split_unmapped() is used in
folio_split_unmapped(). According to its comment, it could take device-private
folio.

This means for device-private folio, we still lock lru_list and try to remove
it from deferred_split_lru. The good news is this doesn't harm the system, but
does some extra work.

Would it be better to add !folio_is_device_private() here?

The purpose to lock here is to prevent shrinker seeing ref-0 folio. Since
device-private folio is not on deferred_split_lru, shrink won't see it.

>+	if (dequeue_deferred) {
>+		struct mem_cgroup *memcg;
>+
>+		rcu_read_lock();
>+		memcg = folio_memcg(folio);
>+		lru = list_lru_lock(&deferred_split_lru,
>+				    folio_nid(folio), &memcg);
>+	}
> 	if (folio_ref_freeze(folio, folio_cache_ref_count(folio) + 1)) {
> 		struct swap_cluster_info *ci = NULL;
> 		struct lruvec *lruvec;
> 
>-		if (old_order > 1) {
>-			if (!list_empty(&folio->_deferred_list)) {
>-				ds_queue->split_queue_len--;
>-				/*
>-				 * Reinitialize page_deferred_list after removing the
>-				 * page from the split_queue, otherwise a subsequent
>-				 * split will see list corruption when checking the
>-				 * page_deferred_list.
>-				 */
>-				list_del_init(&folio->_deferred_list);
>-			}
>+		if (dequeue_deferred) {
>+			__list_lru_del(&deferred_split_lru, lru,
>+				       &folio->_deferred_list, folio_nid(folio));
> 			if (folio_test_partially_mapped(folio)) {
> 				folio_clear_partially_mapped(folio);
> 				mod_mthp_stat(old_order,
> 					MTHP_STAT_NR_ANON_PARTIALLY_MAPPED, -1);
> 			}
>+			list_lru_unlock(lru);
>+			rcu_read_unlock();
> 		}
>-		split_queue_unlock(ds_queue);
>+
> 		if (mapping) {
> 			int nr = folio_nr_pages(folio);
> 
>@@ -4017,7 +3940,10 @@ static int __folio_freeze_and_split_unmapped(struct folio *folio, unsigned int n
> 		if (ci)
> 			swap_cluster_unlock(ci);
> 	} else {
>-		split_queue_unlock(ds_queue);
>+		if (dequeue_deferred) {
>+			list_lru_unlock(lru);
>+			rcu_read_unlock();
>+		}
> 		return -EAGAIN;
> 	}
> 

-- 
Wei Yang
Help you, Help me

  parent reply	other threads:[~2026-06-20  7:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-27 20:45 [PATCH v5 0/9] mm: switch THP shrinker to list_lru Johannes Weiner
2026-05-27 20:45 ` [PATCH v5 1/9] mm: list_lru: fix set_shrinker_bit() call during race with cgroup deletion Johannes Weiner
2026-05-28 13:25   ` Usama Arif
2026-05-30  2:38   ` Wei Yang
2026-05-27 20:45 ` [PATCH v5 2/9] mm: list_lru: lock_list_lru_of_memcg() cannot return NULL if !skip_empty Johannes Weiner
2026-05-27 20:45 ` [PATCH v5 3/9] mm: list_lru: deduplicate unlock_list_lru() Johannes Weiner
2026-05-27 20:45 ` [PATCH v5 4/9] mm: list_lru: move list dead check to lock_list_lru_of_memcg() Johannes Weiner
2026-05-27 20:45 ` [PATCH v5 5/9] mm: list_lru: deduplicate lock_list_lru() Johannes Weiner
2026-05-29  9:56   ` Wei Yang
2026-05-29 13:42     ` Johannes Weiner
2026-05-30  1:25       ` Wei Yang
2026-05-27 20:45 ` [PATCH v5 6/9] mm: list_lru: introduce caller locking for additions and deletions Johannes Weiner
2026-05-27 20:45 ` [PATCH v5 7/9] mm: list_lru: introduce folio_memcg_list_lru_alloc() Johannes Weiner
2026-05-27 20:45 ` [PATCH v5 8/9] mm: memory: flatten alloc_anon_folio() retry loop Johannes Weiner
2026-05-30  9:06   ` Dev Jain
2026-05-27 20:45 ` [PATCH v5 9/9] mm: switch deferred split shrinker to list_lru Johannes Weiner
2026-05-28  7:08   ` SeongJae Park
2026-05-28 14:03     ` Johannes Weiner
2026-05-28 13:32   ` Usama Arif
2026-05-28 14:02     ` Johannes Weiner
2026-05-28 15:31       ` Usama Arif
2026-05-29 17:33   ` Kairui Song
2026-05-31  8:00   ` Wei Yang
2026-06-01 10:39   ` Lance Yang
2026-06-01 11:09     ` Lance Yang
2026-06-01 13:21   ` Lance Yang
2026-06-01 18:17     ` Johannes Weiner
2026-06-09  3:20       ` Lance Yang
2026-06-09  7:35         ` Lorenzo Stoakes
2026-06-09  8:02           ` Lance Yang
2026-06-20  7:39   ` Wei Yang [this message]
2026-06-01  8:36 ` [PATCH v5 0/9] mm: switch THP " Lance Yang
2026-06-02 21:46   ` Johannes Weiner
2026-06-03  4:44     ` Lance Yang
2026-06-03 11:41       ` Johannes Weiner
2026-06-03 11:53         ` Lance Yang

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=20260620073916.ico5v2kji4skpf5m@master \
    --to=richard.weiyang@gmail.com \
    --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=hannes@cmpxchg.org \
    --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=usama.arif@linux.dev \
    --cc=vbabka@kernel.org \
    --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