[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aTpGwg7tHfDJzek9@MiWiFi-R3L-srv>
Date: Thu, 11 Dec 2025 12:21:22 +0800
From: Baoquan He <bhe@...hat.com>
To: Kairui Song <ryncsn@...il.com>
Cc: linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>,
Barry Song <baohua@...nel.org>, Chris Li <chrisl@...nel.org>,
Nhat Pham <nphamcs@...il.com>, Yosry Ahmed <yosry.ahmed@...ux.dev>,
David Hildenbrand <david@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Youngjun Park <youngjun.park@....com>,
Hugh Dickins <hughd@...gle.com>,
Baolin Wang <baolin.wang@...ux.alibaba.com>,
Ying Huang <ying.huang@...ux.alibaba.com>,
Kemeng Shi <shikemeng@...weicloud.com>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>,
"Matthew Wilcox (Oracle)" <willy@...radead.org>,
linux-kernel@...r.kernel.org, Kairui Song <kasong@...cent.com>
Subject: Re: [PATCH v4 06/19] mm, swap: free the swap cache after folio is
mapped
On 12/05/25 at 03:29am, Kairui Song wrote:
> From: Kairui Song <kasong@...cent.com>
>
> To reduce repeated faults due to parallel swapins of the same PTE,
> remove the folio from the swap cache after it is mapped. So new faults
> from the swap PTE will be much more likely to see the folio in the swap
> cache and wait on it. This does not eliminate all swapin races: an
> ongoing swapin fault may still see an empty swap cache. That's harmless,
> as the PTE is changed before the swap cache is cleared, so it will just
> return and not trigger any repeated faults.
It may be clearer to mention that this patch makes change to defer the
swap cache freeing from before pte mapping to after pte mapping.
Other than this nit pick, it looks good to me.
Reviewed-by: Baoquan He <bhe@...hat.com>
>
> Signed-off-by: Kairui Song <kasong@...cent.com>
> ---
> mm/memory.c | 21 +++++++++++----------
> 1 file changed, 11 insertions(+), 10 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 3f707275d540..ce9f56f77ae5 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4362,6 +4362,7 @@ static vm_fault_t remove_device_exclusive_entry(struct vm_fault *vmf)
> static inline bool should_try_to_free_swap(struct swap_info_struct *si,
> struct folio *folio,
> struct vm_area_struct *vma,
> + unsigned int extra_refs,
> unsigned int fault_flags)
> {
> if (!folio_test_swapcache(folio))
> @@ -4384,7 +4385,7 @@ static inline bool should_try_to_free_swap(struct swap_info_struct *si,
> * reference only in case it's likely that we'll be the exclusive user.
> */
> return (fault_flags & FAULT_FLAG_WRITE) && !folio_test_ksm(folio) &&
> - folio_ref_count(folio) == (1 + folio_nr_pages(folio));
> + folio_ref_count(folio) == (extra_refs + folio_nr_pages(folio));
> }
>
> static vm_fault_t pte_marker_clear(struct vm_fault *vmf)
> @@ -4936,15 +4937,6 @@ vm_fault_t do_swap_page(struct vm_fault *vmf)
> */
> arch_swap_restore(folio_swap(entry, folio), folio);
>
> - /*
> - * Remove the swap entry and conditionally try to free up the swapcache.
> - * We're already holding a reference on the page but haven't mapped it
> - * yet.
> - */
> - swap_free_nr(entry, nr_pages);
> - if (should_try_to_free_swap(si, folio, vma, vmf->flags))
> - folio_free_swap(folio);
> -
> add_mm_counter(vma->vm_mm, MM_ANONPAGES, nr_pages);
> add_mm_counter(vma->vm_mm, MM_SWAPENTS, -nr_pages);
> pte = mk_pte(page, vma->vm_page_prot);
> @@ -4998,6 +4990,15 @@ vm_fault_t do_swap_page(struct vm_fault *vmf)
> arch_do_swap_page_nr(vma->vm_mm, vma, address,
> pte, pte, nr_pages);
>
> + /*
> + * Remove the swap entry and conditionally try to free up the swapcache.
> + * Do it after mapping, so raced page faults will likely see the folio
> + * in swap cache and wait on the folio lock.
> + */
> + swap_free_nr(entry, nr_pages);
> + if (should_try_to_free_swap(si, folio, vma, nr_pages, vmf->flags))
> + folio_free_swap(folio);
> +
> folio_unlock(folio);
> if (unlikely(folio != swapcache)) {
> /*
>
> --
> 2.52.0
>
Powered by blists - more mailing lists