From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: akpm@linux-foundation.org, hannes@cmpxchg.org
Cc: david@redhat.com, mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, lorenzo.stoakes@oracle.com,
hughd@google.com, willy@infradead.org,
baolin.wang@linux.alibaba.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] some cleanups for pageout()
Date: Thu, 18 Sep 2025 11:46:52 +0800 [thread overview]
Message-ID: <cover.1758166683.git.baolin.wang@linux.alibaba.com> (raw)
Since we no longer attempt to write back filesystem folios in pageout(),
and only tmpfs/shmem folios and anonymous swapcache folios can be written
back, we can remove the redundant folio_test_private() related logic to
simplify the logic of pageout(), as tmpfs/shmem and swapcache folios do
not use the PG_private flag.
Changes from v1:
- Re-write the commit message for patch 1 after discussing with Hugh. Thanks.
- Add a warning to catch this unlikely case.
- Add acked tags. Thanks.
Baolin Wang (2):
mm: vmscan: remove folio_test_private() check in pageout()
mm: vmscan: simplify the folio refcount check in pageout()
mm/vmscan.c | 28 +++++++---------------------
1 file changed, 7 insertions(+), 21 deletions(-)
--
2.43.7
next reply other threads:[~2025-09-18 3:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 3:46 Baolin Wang [this message]
2025-09-18 3:46 ` [PATCH v2 1/2] mm: vmscan: remove folio_test_private() check in pageout() Baolin Wang
2025-09-18 6:00 ` David Hildenbrand
2025-09-18 9:36 ` Baolin Wang
2025-09-19 1:06 ` Shakeel Butt
2025-09-19 2:12 ` Baolin Wang
2025-09-19 8:00 ` David Hildenbrand
2025-09-22 5:32 ` Hugh Dickins
2025-09-22 6:02 ` Baolin Wang
2025-09-18 3:46 ` [PATCH v2 2/2] mm: vmscan: simplify the folio refcount " Baolin Wang
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=cover.1758166683.git.baolin.wang@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=willy@infradead.org \
--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