From: Chris Li <chrisl@kernel.org>
To: kasong@tencent.com
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Nhat Pham <nphamcs@gmail.com>, Baoquan He <bhe@redhat.com>,
Barry Song <baohua@kernel.org>,
Johannes Weiner <hannes@cmpxchg.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Youngjun Park <youngjun.park@lge.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 12/12] mm, swap: no need to clear the shadow explicitly
Date: Wed, 18 Feb 2026 23:19:23 -0800 [thread overview]
Message-ID: <CACePvbU5B3+KEy+Xf1AeKR47QxDWoimM18bp0fZE1s8etLBkwg@mail.gmail.com> (raw)
In-Reply-To: <20260218-swap-table-p3-v3-12-f4e34be021a7@tencent.com>
On Tue, Feb 17, 2026 at 12:06 PM Kairui Song via B4 Relay
<devnull+kasong.tencent.com@kernel.org> wrote:
>
> From: Kairui Song <kasong@tencent.com>
>
> Since we no longer bypass the swap cache, every swap-in will clear the
> swap shadow by inserting the folio into the swap table. The only place
> we may seem to need to free the swap shadow is when the swap slots are
> freed directly without a folio (swap_put_entries_direct). But with the
> swap table, that is not needed either. Freeing a slot in the swap table
> will set the table entry to NULL, which erases the shadow just fine.
>
> So just delete all explicit shadow clearing, it's no longer needed.
> Also, rearrange the freeing.
>
> Signed-off-by: Kairui Song <kasong@tencent.com>
Acked-by: Chris Li <chrisl@kernel.org>
Chris
> ---
> mm/swap.h | 1 -
> mm/swap_state.c | 21 ---------------------
> mm/swapfile.c | 2 --
> 3 files changed, 24 deletions(-)
>
> diff --git a/mm/swap.h b/mm/swap.h
> index 9728e6a944b2..a77016f2423b 100644
> --- a/mm/swap.h
> +++ b/mm/swap.h
> @@ -290,7 +290,6 @@ void __swap_cache_del_folio(struct swap_cluster_info *ci,
> struct folio *folio, swp_entry_t entry, void *shadow);
> void __swap_cache_replace_folio(struct swap_cluster_info *ci,
> struct folio *old, struct folio *new);
> -void __swap_cache_clear_shadow(swp_entry_t entry, int nr_ents);
>
> void show_swap_cache_info(void);
> void swapcache_clear(struct swap_info_struct *si, swp_entry_t entry, int nr);
> diff --git a/mm/swap_state.c b/mm/swap_state.c
> index e7618ffe6d70..32d9d877bda8 100644
> --- a/mm/swap_state.c
> +++ b/mm/swap_state.c
> @@ -350,27 +350,6 @@ void __swap_cache_replace_folio(struct swap_cluster_info *ci,
> }
> }
>
> -/**
> - * __swap_cache_clear_shadow - Clears a set of shadows in the swap cache.
> - * @entry: The starting index entry.
> - * @nr_ents: How many slots need to be cleared.
> - *
> - * Context: Caller must ensure the range is valid, all in one single cluster,
> - * not occupied by any folio, and lock the cluster.
> - */
> -void __swap_cache_clear_shadow(swp_entry_t entry, int nr_ents)
> -{
> - struct swap_cluster_info *ci = __swap_entry_to_cluster(entry);
> - unsigned int ci_off = swp_cluster_offset(entry), ci_end;
> - unsigned long old;
> -
> - ci_end = ci_off + nr_ents;
> - do {
> - old = __swap_table_xchg(ci, ci_off, null_to_swp_tb());
> - WARN_ON_ONCE(swp_tb_is_folio(old) || swp_tb_get_count(old));
> - } while (++ci_off < ci_end);
> -}
> -
> /*
> * If we are the only user, then try to free up the swap cache.
> *
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index dab5e726855b..802efa37b33f 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1287,7 +1287,6 @@ static void swap_range_alloc(struct swap_info_struct *si,
> static void swap_range_free(struct swap_info_struct *si, unsigned long offset,
> unsigned int nr_entries)
> {
> - unsigned long begin = offset;
> unsigned long end = offset + nr_entries - 1;
> void (*swap_slot_free_notify)(struct block_device *, unsigned long);
> unsigned int i;
> @@ -1312,7 +1311,6 @@ static void swap_range_free(struct swap_info_struct *si, unsigned long offset,
> swap_slot_free_notify(si->bdev, offset);
> offset++;
> }
> - __swap_cache_clear_shadow(swp_entry(si->type, begin), nr_entries);
>
> /*
> * Make sure that try_to_unuse() observes si->inuse_pages reaching 0
>
> --
> 2.52.0
>
>
next prev parent reply other threads:[~2026-02-19 7:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 20:06 [PATCH v3 00/12] mm, swap: swap table phase III: remove swap_map Kairui Song via B4 Relay
2026-02-17 20:06 ` [PATCH v3 01/12] mm, swap: protect si->swap_file properly and use as a mount indicator Kairui Song via B4 Relay
2026-02-19 6:36 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 02/12] mm, swap: clean up swapon process and locking Kairui Song via B4 Relay
2026-02-19 6:45 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 03/12] mm, swap: remove redundant arguments and locking for enabling a device Kairui Song via B4 Relay
2026-02-19 6:48 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 04/12] mm, swap: consolidate bad slots setup and make it more robust Kairui Song via B4 Relay
2026-02-19 6:51 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 05/12] mm/workingset: leave highest bits empty for anon shadow Kairui Song via B4 Relay
2026-02-19 6:56 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 06/12] mm, swap: implement helpers for reserving data in the swap table Kairui Song via B4 Relay
2026-02-19 7:00 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 07/12] mm, swap: mark bad slots in swap table directly Kairui Song via B4 Relay
2026-02-19 7:01 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 08/12] mm, swap: simplify swap table sanity range check Kairui Song via B4 Relay
2026-02-19 7:02 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 09/12] mm, swap: use the swap table to track the swap count Kairui Song via B4 Relay
2026-02-18 10:40 ` kernel test robot
2026-02-18 12:22 ` Kairui Song
2026-02-19 7:06 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 10/12] mm, swap: no need to truncate the scan border Kairui Song via B4 Relay
2026-02-19 7:10 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 11/12] mm, swap: simplify checking if a folio is swapped Kairui Song via B4 Relay
2026-02-19 7:18 ` Chris Li
2026-02-17 20:06 ` [PATCH v3 12/12] mm, swap: no need to clear the shadow explicitly Kairui Song via B4 Relay
2026-02-19 7:19 ` Chris Li [this message]
2026-02-17 20:10 ` [PATCH v3 00/12] mm, swap: swap table phase III: remove swap_map Kairui Song
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=CACePvbU5B3+KEy+Xf1AeKR47QxDWoimM18bp0fZE1s8etLBkwg@mail.gmail.com \
--to=chrisl@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bhe@redhat.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=nphamcs@gmail.com \
--cc=shikemeng@huaweicloud.com \
--cc=youngjun.park@lge.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