From: Hugh Dickins <hughd@google.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: hughd@google.com, willy@infradead.org, david@redhat.com,
wangkefeng.wang@huawei.com, chrisl@kernel.org,
ying.huang@intel.com, 21cnbao@gmail.com, ryan.roberts@arm.com,
shy828301@gmail.com, ziy@nvidia.com, ioworker0@gmail.com,
da.gomez@samsung.com, p.raghav@samsung.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 8/9] mm: shmem: split large entry if the swapin folio is not large
Date: Sun, 25 Aug 2024 15:31:21 -0700 (PDT) [thread overview]
Message-ID: <e2a2ba5d-864c-50aa-7579-97cba1c7dd0c@google.com> (raw)
In-Reply-To: <4a0f12f27c54a62eb4d9ca1265fed3a62531a63e.1723434324.git.baolin.wang@linux.alibaba.com>
On Mon, 12 Aug 2024, Baolin Wang wrote:
> Now the swap device can only swap-in order 0 folio, even though a large
> folio is swapped out. This requires us to split the large entry previously
> saved in the shmem pagecache to support the swap in of small folios.
>
> Signed-off-by: Baolin Wang <baolin.wang@linux.alibaba.com>
> ---
> mm/shmem.c | 100 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 100 insertions(+)
>
> diff --git a/mm/shmem.c b/mm/shmem.c
> index 345e25425e37..996062dc196b 100644
> --- a/mm/shmem.c
> +++ b/mm/shmem.c
> @@ -1990,6 +1990,81 @@ static void shmem_set_folio_swapin_error(struct inode *inode, pgoff_t index,
> swap_free_nr(swap, nr_pages);
> }
>
> +static int shmem_split_large_entry(struct inode *inode, pgoff_t index,
> + swp_entry_t swap, int new_order, gfp_t gfp)
> +{
> + struct address_space *mapping = inode->i_mapping;
> + XA_STATE_ORDER(xas, &mapping->i_pages, index, new_order);
> + void *alloced_shadow = NULL;
> + int alloced_order = 0, i;
gfp needs to be adjusted: see fix patch below.
> +
> + for (;;) {
> + int order = -1, split_order = 0;
> + void *old = NULL;
> +
> + xas_lock_irq(&xas);
> + old = xas_load(&xas);
> + if (!xa_is_value(old) || swp_to_radix_entry(swap) != old) {
> + xas_set_err(&xas, -EEXIST);
> + goto unlock;
> + }
> +
> + order = xas_get_order(&xas);
> +
> + /* Swap entry may have changed before we re-acquire the lock */
> + if (alloced_order &&
> + (old != alloced_shadow || order != alloced_order)) {
> + xas_destroy(&xas);
> + alloced_order = 0;
> + }
> +
> + /* Try to split large swap entry in pagecache */
> + if (order > 0 && order > new_order) {
I have not even attempted to understand all the manipulations of order and
new_order and alloced_order and split_order. And further down it turns out
that this is only ever called with new_order 0.
You may be wanting to cater for more generality in future, but for now
please cut this down to the new_order 0 case, and omit that parameter.
It will be easier for us to think about the xa_get_order() races if
the possibilities are more limited.
> + if (!alloced_order) {
> + split_order = order;
> + goto unlock;
> + }
> + xas_split(&xas, old, order);
> +
> + /*
> + * Re-set the swap entry after splitting, and the swap
> + * offset of the original large entry must be continuous.
> + */
> + for (i = 0; i < 1 << order; i += (1 << new_order)) {
> + pgoff_t aligned_index = round_down(index, 1 << order);
> + swp_entry_t tmp;
> +
> + tmp = swp_entry(swp_type(swap), swp_offset(swap) + i);
> + __xa_store(&mapping->i_pages, aligned_index + i,
> + swp_to_radix_entry(tmp), 0);
> + }
So that is done under xas lock: good. But is the intermediate state
visible to RCU readers, and could that be a problem?
> + }
> +
> +unlock:
> + xas_unlock_irq(&xas);
> +
> + /* split needed, alloc here and retry. */
> + if (split_order) {
> + xas_split_alloc(&xas, old, split_order, gfp);
> + if (xas_error(&xas))
> + goto error;
> + alloced_shadow = old;
> + alloced_order = split_order;
> + xas_reset(&xas);
> + continue;
> + }
> +
> + if (!xas_nomem(&xas, gfp))
> + break;
> + }
> +
> +error:
> + if (xas_error(&xas))
> + return xas_error(&xas);
> +
> + return alloced_order;
> +}
> +
> /*
> * Swap in the folio pointed to by *foliop.
> * Caller has to make sure that *foliop contains a valid swapped folio.
> @@ -2026,12 +2101,37 @@ static int shmem_swapin_folio(struct inode *inode, pgoff_t index,
> /* Look it up and read it in.. */
> folio = swap_cache_get_folio(swap, NULL, 0);
> if (!folio) {
> + int split_order;
> +
> /* Or update major stats only when swapin succeeds?? */
> if (fault_type) {
> *fault_type |= VM_FAULT_MAJOR;
> count_vm_event(PGMAJFAULT);
> count_memcg_event_mm(fault_mm, PGMAJFAULT);
> }
> +
> + /*
> + * Now swap device can only swap in order 0 folio, then we
> + * should split the large swap entry stored in the pagecache
> + * if necessary.
> + */
> + split_order = shmem_split_large_entry(inode, index, swap, 0, gfp);
> + if (split_order < 0) {
> + error = split_order;
> + goto failed;
> + }
> +
> + /*
> + * If the large swap entry has already been split, it is
> + * necessary to recalculate the new swap entry based on
> + * the old order alignment.
> + */
> + if (split_order > 0) {
> + pgoff_t offset = index - round_down(index, 1 << split_order);
> +
> + swap = swp_entry(swp_type(swap), swp_offset(swap) + offset);
> + }
> +
> /* Here we actually start the io */
> folio = shmem_swapin_cluster(swap, gfp, info, index);
> if (!folio) {
> --
[PATCH] mm: shmem: split large entry if the swapin folio is not large fix
Fix all the
Unexpected gfp: 0x2 (__GFP_HIGHMEM). Fixing up to gfp: 0x1120d0
(__GFP_IO|__GFP_FS|__GFP_NOWARN|__GFP_NORETRY|__GFP_HARDWALL|__GFP_RECLAIMABLE).
Fix your code!
warnings from kmalloc_fix_flags() from xas_split_alloc() from
shmem_split_large_entry().
Fixes: a960844d5ac9 ("mm: shmem: split large entry if the swapin folio is not large")
Signed-off-by: Hugh Dickins <hughd@google.com>
---
mm/shmem.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mm/shmem.c b/mm/shmem.c
index ae2245dce8ae..85e3bd3e709e 100644
--- a/mm/shmem.c
+++ b/mm/shmem.c
@@ -1999,6 +1999,9 @@ static int shmem_split_large_entry(struct inode *inode, pgoff_t index,
void *alloced_shadow = NULL;
int alloced_order = 0, i;
+ /* Convert user data gfp flags to xarray node gfp flags */
+ gfp &= GFP_RECLAIM_MASK;
+
for (;;) {
int order = -1, split_order = 0;
void *old = NULL;
--
2.35.3
next prev parent reply other threads:[~2024-08-25 22:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 7:42 [PATCH v5 0/9] support large folio swap-out and swap-in for shmem Baolin Wang
2024-08-12 7:42 ` [PATCH v5 1/9] mm: swap: extend swap_shmem_alloc() to support batch SWAP_MAP_SHMEM flag setting Baolin Wang
2024-08-12 7:42 ` [PATCH v5 2/9] mm: shmem: extend shmem_partial_swap_usage() to support large folio swap Baolin Wang
2024-08-12 7:42 ` [PATCH v5 3/9] mm: shmem: return number of pages beeing freed in shmem_free_swap Baolin Wang
2024-08-12 7:42 ` [PATCH v5 4/9] mm: filemap: use xa_get_order() to get the swap entry order Baolin Wang
2024-08-25 21:55 ` Hugh Dickins
2024-08-25 23:28 ` Matthew Wilcox
2024-08-27 10:10 ` Baolin Wang
2024-08-29 8:07 ` Hugh Dickins
2024-08-29 12:40 ` Baolin Wang
2024-08-30 10:18 ` Hugh Dickins
2024-08-12 7:42 ` [PATCH v5 5/9] mm: shmem: use swap_free_nr() to free shmem swap entries Baolin Wang
2024-08-12 7:42 ` [PATCH v5 6/9] mm: shmem: support large folio allocation for shmem_replace_folio() Baolin Wang
2024-08-25 22:05 ` Hugh Dickins
2024-08-27 3:06 ` Baolin Wang
2024-08-12 7:42 ` [PATCH v5 7/9] mm: shmem: drop folio reference count using 'nr_pages' in shmem_delete_from_page_cache() Baolin Wang
2024-08-12 7:42 ` [PATCH v5 8/9] mm: shmem: split large entry if the swapin folio is not large Baolin Wang
2024-08-25 22:31 ` Hugh Dickins [this message]
2024-08-27 6:46 ` Baolin Wang
2024-08-12 7:42 ` [PATCH v5 9/9] mm: shmem: support large folio swap out Baolin Wang
2024-08-25 23:14 ` Hugh Dickins
2024-08-27 6:58 ` Baolin Wang
2024-08-28 8:28 ` [PATCH] mm: shmem: support large folio swap out fix 2 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=e2a2ba5d-864c-50aa-7579-97cba1c7dd0c@google.com \
--to=hughd@google.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=da.gomez@samsung.com \
--cc=david@redhat.com \
--cc=ioworker0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=p.raghav@samsung.com \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=wangkefeng.wang@huawei.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=ziy@nvidia.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