linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Kairui Song <ryncsn@gmail.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Barry Song <baohua@kernel.org>, Chris Li <chrisl@kernel.org>,
	Nhat Pham <nphamcs@gmail.com>,
	Yosry Ahmed <yosry.ahmed@linux.dev>,
	David Hildenbrand <david@kernel.org>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Youngjun Park <youngjun.park@lge.com>,
	Hugh Dickins <hughd@google.com>,
	Baolin Wang <baolin.wang@linux.alibaba.com>,
	Ying Huang <ying.huang@linux.alibaba.com>,
	Kemeng Shi <shikemeng@huaweicloud.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	linux-kernel@vger.kernel.org, Kairui Song <kasong@tencent.com>
Subject: Re: [PATCH v4 09/19] mm, swap: swap entry of a bad slot should not be considered as swapped out
Date: Mon, 15 Dec 2025 11:57:33 +0800	[thread overview]
Message-ID: <aT+HLZJRgmvca7K2@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20251205-swap-table-p2-v4-9-cb7e28a26a40@tencent.com>

On 12/05/25 at 03:29am, Kairui Song wrote:
> From: Kairui Song <kasong@tencent.com>
> 
> When checking if a swap entry is swapped out, we simply check if the
> bitwise result of the count value is larger than 0. But SWAP_MAP_BAD
> will also be considered as a swao count value larger than 0.
> 
> SWAP_MAP_BAD being considered as a count value larger than 0 is useful
> for the swap allocator: they will be seen as a used slot, so the
> allocator will skip them. But for the swapped out check, this
> isn't correct.
> 
> There is currently no observable issue. The swapped out check is only
> useful for readahead and folio swapped-out status check. For readahead,
> the swap cache layer will abort upon checking and updating the swap map.
> For the folio swapped out status check, the swap allocator will never
> allocate an entry of bad slots to folio, so that part is fine too. The
> worst that could happen now is redundant allocation/freeing of folios
> and waste CPU time.
> 
> This also makes it easier to get rid of swap map checking and update
> during folio insertion in the swap cache layer.

Will swap_entry_swapped() be called in other places in phase 3 of swap
table?

I checked the code of the current phase 2, in all three places you
convert it with swp_offset(entry), is it necessary? Why don't you keep
the swap_entry_swapped(si, entry)? Surely, this is trivial.

mm/swap_state.c <<swap_cache_alloc_folio>>
if (!swap_entry_swapped(si, swp_offset(entry)))
mm/swapfile.c <<folio_swapped>>
return swap_entry_swapped(si, swp_offset(entry));
mm/swapfile.c <<swap_free_hibernation_slot>>
             WARN_ON(swap_entry_swapped(si, offset));

> 
> Signed-off-by: Kairui Song <kasong@tencent.com>
> ---
>  include/linux/swap.h |  6 ++++--
>  mm/swap_state.c      |  4 ++--
>  mm/swapfile.c        | 22 +++++++++++-----------
>  3 files changed, 17 insertions(+), 15 deletions(-)
> 
> diff --git a/include/linux/swap.h b/include/linux/swap.h
> index bf72b548a96d..936fa8f9e5f3 100644
> --- a/include/linux/swap.h
> +++ b/include/linux/swap.h
> @@ -466,7 +466,8 @@ int find_first_swap(dev_t *device);
>  extern unsigned int count_swap_pages(int, int);
>  extern sector_t swapdev_block(int, pgoff_t);
>  extern int __swap_count(swp_entry_t entry);
> -extern bool swap_entry_swapped(struct swap_info_struct *si, swp_entry_t entry);
> +extern bool swap_entry_swapped(struct swap_info_struct *si,
> +			       unsigned long offset);
>  extern int swp_swapcount(swp_entry_t entry);
>  struct backing_dev_info;
>  extern struct swap_info_struct *get_swap_device(swp_entry_t entry);
> @@ -535,7 +536,8 @@ static inline int __swap_count(swp_entry_t entry)
>  	return 0;
>  }
>  
> -static inline bool swap_entry_swapped(struct swap_info_struct *si, swp_entry_t entry)
> +static inline bool swap_entry_swapped(struct swap_info_struct *si,
> +				      unsigned long offset)
>  {
>  	return false;
>  }
> diff --git a/mm/swap_state.c b/mm/swap_state.c
> index 8c429dc33ca9..0c5aad537716 100644
> --- a/mm/swap_state.c
> +++ b/mm/swap_state.c
> @@ -527,8 +527,8 @@ struct folio *swap_cache_alloc_folio(swp_entry_t entry, gfp_t gfp_mask,
>  	if (folio)
>  		return folio;
>  
> -	/* Skip allocation for unused swap slot for readahead path. */
> -	if (!swap_entry_swapped(si, entry))
> +	/* Skip allocation for unused and bad swap slot for readahead. */
> +	if (!swap_entry_swapped(si, swp_offset(entry)))
>  		return NULL;
>  
>  	/* Allocate a new folio to be added into the swap cache. */
> diff --git a/mm/swapfile.c b/mm/swapfile.c
> index e23287c06f1c..5a766d4fcaa5 100644
> --- a/mm/swapfile.c
> +++ b/mm/swapfile.c
> @@ -1766,21 +1766,21 @@ int __swap_count(swp_entry_t entry)
>  	return swap_count(si->swap_map[offset]);
>  }
>  
> -/*
> - * How many references to @entry are currently swapped out?
> - * This does not give an exact answer when swap count is continued,
> - * but does include the high COUNT_CONTINUED flag to allow for that.
> +/**
> + * swap_entry_swapped - Check if the swap entry at @offset is swapped.
> + * @si: the swap device.
> + * @offset: offset of the swap entry.
>   */
> -bool swap_entry_swapped(struct swap_info_struct *si, swp_entry_t entry)
> +bool swap_entry_swapped(struct swap_info_struct *si, unsigned long offset)
>  {
> -	pgoff_t offset = swp_offset(entry);
>  	struct swap_cluster_info *ci;
>  	int count;
>  
>  	ci = swap_cluster_lock(si, offset);
>  	count = swap_count(si->swap_map[offset]);
>  	swap_cluster_unlock(ci);
> -	return !!count;
> +
> +	return count && count != SWAP_MAP_BAD;
>  }
>  
>  /*
> @@ -1866,7 +1866,7 @@ static bool folio_swapped(struct folio *folio)
>  		return false;
>  
>  	if (!IS_ENABLED(CONFIG_THP_SWAP) || likely(!folio_test_large(folio)))
> -		return swap_entry_swapped(si, entry);
> +		return swap_entry_swapped(si, swp_offset(entry));
>  
>  	return swap_page_trans_huge_swapped(si, entry, folio_order(folio));
>  }
> @@ -3677,10 +3677,10 @@ static int __swap_duplicate(swp_entry_t entry, unsigned char usage, int nr)
>  		count = si->swap_map[offset + i];
>  
>  		/*
> -		 * swapin_readahead() doesn't check if a swap entry is valid, so the
> -		 * swap entry could be SWAP_MAP_BAD. Check here with lock held.
> +		 * Allocator never allocates bad slots, and readahead is guarded
> +		 * by swap_entry_swapped.
>  		 */
> -		if (unlikely(swap_count(count) == SWAP_MAP_BAD)) {
> +		if (WARN_ON(swap_count(count) == SWAP_MAP_BAD)) {
>  			err = -ENOENT;
>  			goto unlock_out;
>  		}
> 
> -- 
> 2.52.0
> 



  reply	other threads:[~2025-12-15  3:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-04 19:29 [PATCH v4 00/19] mm, swap: swap table phase II: unify swapin use swap cache and cleanup flags Kairui Song
2025-12-04 19:29 ` [PATCH v4 01/19] mm, swap: rename __read_swap_cache_async to swap_cache_alloc_folio Kairui Song
2025-12-11  1:01   ` Baoquan He
2025-12-04 19:29 ` [PATCH v4 02/19] mm, swap: split swap cache preparation loop into a standalone helper Kairui Song
2025-12-04 19:29 ` [PATCH v4 03/19] mm, swap: never bypass the swap cache even for SWP_SYNCHRONOUS_IO Kairui Song
2025-12-04 19:29 ` [PATCH v4 04/19] mm, swap: always try to free swap cache for SWP_SYNCHRONOUS_IO devices Kairui Song
2025-12-04 19:29 ` [PATCH v4 05/19] mm, swap: simplify the code and reduce indention Kairui Song
2025-12-04 19:29 ` [PATCH v4 06/19] mm, swap: free the swap cache after folio is mapped Kairui Song
2025-12-11  4:21   ` Baoquan He
2025-12-04 19:29 ` [PATCH v4 07/19] mm/shmem: never bypass the swap cache for SWP_SYNCHRONOUS_IO Kairui Song
2025-12-04 19:29 ` [PATCH v4 08/19] mm/shmem, swap: remove SWAP_MAP_SHMEM Kairui Song
2025-12-04 19:29 ` [PATCH v4 09/19] mm, swap: swap entry of a bad slot should not be considered as swapped out Kairui Song
2025-12-15  3:57   ` Baoquan He [this message]
2025-12-15  4:12     ` Kairui Song
2025-12-04 19:29 ` [PATCH v4 10/19] mm, swap: consolidate cluster reclaim and usability check Kairui Song
2025-12-15  4:12   ` Baoquan He
2025-12-15  4:38     ` Kairui Song
2025-12-04 19:29 ` [PATCH v4 11/19] mm, swap: split locked entry duplicating into a standalone helper Kairui Song
2025-12-04 19:29 ` [PATCH v4 12/19] mm, swap: use swap cache as the swap in synchronize layer Kairui Song
2025-12-04 19:29 ` [PATCH v4 13/19] mm, swap: remove workaround for unsynchronized swap map cache state Kairui Song
2025-12-04 19:29 ` [PATCH v4 14/19] mm, swap: cleanup swap entry management workflow Kairui Song
2025-12-04 19:29 ` [PATCH v4 15/19] mm, swap: add folio to swap cache directly on allocation Kairui Song
2025-12-04 19:29 ` [PATCH v4 16/19] mm, swap: check swap table directly for checking cache Kairui Song
2025-12-04 19:29 ` [PATCH v4 17/19] mm, swap: clean up and improve swap entries freeing Kairui Song
2025-12-04 19:29 ` [PATCH v4 18/19] mm, swap: drop the SWAP_HAS_CACHE flag Kairui Song
2025-12-04 19:29 ` [PATCH v4 19/19] mm, swap: remove no longer needed _swap_info_get 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=aT+HLZJRgmvca7K2@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=chrisl@kernel.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --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=ryncsn@gmail.com \
    --cc=shikemeng@huaweicloud.com \
    --cc=willy@infradead.org \
    --cc=ying.huang@linux.alibaba.com \
    --cc=yosry.ahmed@linux.dev \
    --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;
as well as URLs for NNTP newsgroup(s).