From: Baoquan He <bhe@redhat.com>
To: Kairui Song <kasong@tencent.com>
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Chris Li <chrisl@kernel.org>, Barry Song <v-songbaohua@oppo.com>,
Hugh Dickins <hughd@google.com>,
Yosry Ahmed <yosryahmed@google.com>,
"Huang, Ying" <ying.huang@linux.alibaba.com>,
Nhat Pham <nphamcs@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Kalesh Singh <kaleshsingh@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] mm, swap: remove swap slot cache
Date: Thu, 20 Feb 2025 15:55:58 +0800 [thread overview]
Message-ID: <Z7bgDhZmg9Vs+btw@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20250214175709.76029-7-ryncsn@gmail.com>
Hi Kairui,
On 02/15/25 at 01:57am, Kairui Song wrote:
......snip....
> -int get_swap_pages(int n_goal, swp_entry_t swp_entries[], int entry_order)
> +swp_entry_t folio_alloc_swap(struct folio *folio)
> {
> - int order = swap_entry_order(entry_order);
> - unsigned long size = 1 << order;
> + unsigned int order = folio_order(folio);
> + unsigned int size = 1 << order;
> struct swap_info_struct *si, *next;
> - int n_ret = 0;
> + swp_entry_t entry = {};
> + unsigned long offset;
> int node;
>
> + if (order) {
> + /*
> + * Should not even be attempting large allocations when huge
> + * page swap is disabled. Warn and fail the allocation.
> + */
> + if (!IS_ENABLED(CONFIG_THP_SWAP) || size > SWAPFILE_CLUSTER) {
> + VM_WARN_ON_ONCE(1);
> + return entry;
> + }
> + }
> +
> /* Fast path using percpu cluster */
> local_lock(&percpu_swap_cluster.lock);
> - n_ret = swap_alloc_fast(swp_entries,
> - SWAP_HAS_CACHE,
> - order, n_goal);
> - if (n_ret == n_goal)
> - goto out;
> + if (swap_alloc_fast(&entry, SWAP_HAS_CACHE, order))
> + goto out_alloced;
>
> - n_goal = min_t(int, n_goal - n_ret, SWAP_BATCH);
> /* Rotate the device and switch to a new cluster */
> spin_lock(&swap_avail_lock);
> start_over:
> @@ -1268,11 +1236,14 @@ int get_swap_pages(int n_goal, swp_entry_t swp_entries[], int entry_order)
> plist_requeue(&si->avail_lists[node], &swap_avail_heads[node]);
> spin_unlock(&swap_avail_lock);
> if (get_swap_device_info(si)) {
> - n_ret += scan_swap_map_slots(si, SWAP_HAS_CACHE, n_goal,
> - swp_entries + n_ret, order);
> + offset = cluster_alloc_swap_entry(si, order, SWAP_HAS_CACHE);
> put_swap_device(si);
> - if (n_ret || size > 1)
> - goto out;
> + if (offset) {
> + entry = swp_entry(si->type, offset);
> + goto out_alloced;
> + }
> + if (order)
> + goto out_failed;
This is not related to this patch, do you know why non order-0 case
can't start over on different devices?
> }
>
> spin_lock(&swap_avail_lock);
> @@ -1291,10 +1262,20 @@ int get_swap_pages(int n_goal, swp_entry_t swp_entries[], int entry_order)
> goto start_over;
> }
> spin_unlock(&swap_avail_lock);
> -out:
> +out_failed:
> + local_unlock(&percpu_swap_cluster.lock);
> + return entry;
> +
> +out_alloced:
> local_unlock(&percpu_swap_cluster.lock);
> - atomic_long_sub(n_ret * size, &nr_swap_pages);
> - return n_ret;
> + if (mem_cgroup_try_charge_swap(folio, entry)) {
> + put_swap_folio(folio, entry);
> + entry.val = 0;
> + } else {
> + atomic_long_sub(size, &nr_swap_pages);
> + }
> +
> + return entry;
> }
>
> static struct swap_info_struct *_swap_info_get(swp_entry_t entry)
......snip....
> @@ -2623,16 +2591,6 @@ static bool __has_usable_swap(void)
> return !plist_head_empty(&swap_active_head);
> }
seems the __has_usable_swap() function need be moved into the ifdeffery
scope where __folio_throttle_swaprate() is located to fix the lkp
warning.
>
> -bool has_usable_swap(void)
> -{
> - bool ret;
> -
> - spin_lock(&swap_lock);
> - ret = __has_usable_swap();
> - spin_unlock(&swap_lock);
> - return ret;
> -}
> -
> /*
> * Called after clearing SWP_WRITEOK, ensures cluster_alloc_range
> * see the updated flags, so there will be no more allocations.
Other than the test robot reported warning, this patch looks good to me.
Thanks.
next prev parent reply other threads:[~2025-02-20 7:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 17:57 [PATCH 0/7] " Kairui Song
2025-02-14 17:57 ` [PATCH 1/7] mm, swap: avoid reclaiming irrelevant swap cache Kairui Song
2025-02-19 2:11 ` Baoquan He
2025-02-14 17:57 ` [PATCH 2/7] mm, swap: drop the flag TTRS_DIRECT Kairui Song
2025-02-19 2:42 ` Baoquan He
2025-02-14 17:57 ` [PATCH 3/7] mm, swap: avoid redundant swap device pinning Kairui Song
2025-02-19 3:35 ` Baoquan He
2025-02-14 17:57 ` [PATCH 4/7] mm, swap: don't update the counter up-front Kairui Song
2025-02-14 17:57 ` [PATCH 5/7] mm, swap: use percpu cluster as allocation fast path Kairui Song
2025-02-19 7:53 ` Baoquan He
2025-02-19 8:34 ` Kairui Song
2025-02-19 9:26 ` Baoquan He
2025-02-19 10:55 ` Baoquan He
2025-02-19 11:12 ` Kairui Song
2025-02-20 2:35 ` Baoquan He
2025-02-20 2:48 ` Kairui Song
2025-02-20 3:24 ` Baoquan He
2025-02-14 17:57 ` [PATCH 6/7] mm, swap: remove swap slot cache Kairui Song
2025-02-15 16:23 ` kernel test robot
2025-02-20 7:55 ` Baoquan He [this message]
2025-02-24 3:16 ` Kairui Song
2025-02-14 17:57 ` [PATCH 7/7] mm, swap: simplify folio swap allocation Kairui Song
2025-02-14 20:13 ` Matthew Wilcox
2025-02-15 6:40 ` Kairui Song
2025-02-15 16:43 ` kernel test robot
2025-02-15 16:54 ` kernel test robot
2025-02-20 10:41 ` Baoquan He
2025-02-15 10:27 ` [PATCH 0/7] mm, swap: remove swap slot cache Baoquan He
2025-02-15 13:34 ` Kairui Song
2025-02-15 15:07 ` Baoquan He
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=Z7bgDhZmg9Vs+btw@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=chrisl@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kaleshsingh@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=v-songbaohua@oppo.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yosryahmed@google.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