From: Baoquan He <baoquan.he@linux.dev>
To: Kairui Song <ryncsn@gmail.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org, chrisl@kernel.org,
usama.arif@linux.dev, baohua@kernel.org, nphamcs@gmail.com,
shikemeng@huaweicloud.com, youngjun.park@lge.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/3] mm/swap: use swap_ops to register swap device's methods
Date: Thu, 14 May 2026 10:06:10 +0800 [thread overview]
Message-ID: <agUuEizORebR3A0O@MiWiFi-R3L-srv> (raw)
In-Reply-To: <CAMgjq7Ap=hEmHg+5Da=NdOQS1JK1FY+WepmW=3HEC4XHfsUmuw@mail.gmail.com>
On 05/13/26 at 01:53am, Kairui Song wrote:
> On Tue, May 12, 2026 at 6:50 PM Baoquan He <baoquan.he@linux.dev> wrote:
> >
> > This simplifies codes and makes logic clearer. And also makes later any
> > new swap device type being added easier to handle.
> >
> > Currently there are three types of swap devices: bdev_fs, bdev_sync
> > and bdev_async, and only operations read_folio and write_folio are
> > included. In the future, there could be more swap device types added
> > and more appropriate opeations adapted into swap_ops.
>
> opeations -> operations
Will fix, thanks.
>
> >
> > Suggested-by: Chris Li <chrisl@kernel.org>
> > Acked-by: Chris Li <chrisl@kernel.org>
> > Co-developed-by: Barry Song <baohua@kernel.org>
> > Signed-off-by: Barry Song <baohua@kernel.org>
> > Signed-off-by: Baoquan He <baoquan.he@linux.dev>
>
> A few nitpicks below:
>
> > -void __swap_writepage(struct folio *folio, struct swap_iocb **swap_plug)
> > -{
> > - struct swap_info_struct *sis = __swap_entry_to_info(folio->swap);
> > -
> > - VM_BUG_ON_FOLIO(!folio_test_swapcache(folio), folio);
>
> This sanify check is dropped and not added back in anywhere. This is
> fine, but it might be better to have a similar VM_WARN_ON_FOLIO in
> swap_writeout?
Good catch. In the old code, it's called by both swap_writeout() and
zswap_writeback_entry(). In zswap_writeback_entry(), the folio is
allocated in-place, we don't need to worry about it now. I am fine to
add it back in swap_writeout() because adding it inside all three
swap_write_xxx() is a little too much.
Cscope tag: __swap_writepage
# line filename / context / line
1 288 /home/bhe/code/linux/mm/page_io.c <<swap_writeout>>
__swap_writepage(folio, swap_plug);
2 1053 /home/bhe/code/linux/mm/zswap.c <<zswap_writeback_entry>>
__swap_writepage(folio, NULL);
>
> > void swap_read_folio(struct folio *folio, struct swap_iocb **plug)
> > {
> > struct swap_info_struct *sis = __swap_entry_to_info(folio->swap);
> > @@ -642,13 +664,7 @@ void swap_read_folio(struct folio *folio, struct swap_iocb **plug)
> > /* We have to read from slower devices. Increase zswap protection. */
> > zswap_folio_swapin(folio);
> >
> > - if (data_race(sis->flags & SWP_FS_OPS)) {
> > - swap_read_folio_fs(folio, plug);
> > - } else if (synchronous) {
> > - swap_read_folio_bdev_sync(folio, sis);
> > - } else {
> > - swap_read_folio_bdev_async(folio, sis);
> > - }
> > + sis->ops->read_folio(sis, folio, plug);
> >
> > finish:
> > if (workingset) {
> > diff --git a/mm/swapfile.c b/mm/swapfile.c
> > index 4840fd40f36f..8c42632e6765 100644
> > --- a/mm/swapfile.c
> > +++ b/mm/swapfile.c
> > @@ -3780,6 +3780,15 @@ SYSCALL_DEFINE2(swapon, const char __user *, specialfile, int, swap_flags)
> > goto free_swap_zswap;
> > }
> >
> > + /*
> > + * init_swap_ops() sets si->ops based on flags. It does not need
> > + * swapon_mutex, and must complete before enable_swap_info()
> > + * exposes the device.
> > + */
> > + error = init_swap_ops(si);
> > + if (error)
> > + goto bad_swap_unlock_inode;
>
> I checked the comment above previously and it looked good. But the
> error label seems not that correct after double check. inode->i_flags
> will keep the S_SWAPFILE flag. Maybe something like add a
> inode->i_flags &= ~S_SWAPFILE here and goto free_swap_zswap. Sorry I
> didn't check this part carefully last time.
Right. How about moving it zswap_swapon() because it only relies on
si->flags setting currently?
>
> But fortunately, init_swap_ops will never fail at this moment so the
> issue never triggers.
>
> > +
> > mutex_lock(&swapon_mutex);
> > prio = DEF_SWAP_PRIO;
> > if (swap_flags & SWAP_FLAG_PREFER)
> > diff --git a/mm/zswap.c b/mm/zswap.c
> > index 4b5149173b0e..192401f46de4 100644
> > --- a/mm/zswap.c
> > +++ b/mm/zswap.c
> > @@ -1054,7 +1054,7 @@ static int zswap_writeback_entry(struct zswap_entry *entry,
> > folio_set_reclaim(folio);
> >
> > /* start writeback */
> > - __swap_writepage(folio, NULL);
> > + si->ops->write_folio(si, folio, NULL);
> >
> > out:
> > if (ret && ret != -EEXIST) {
> > --
> > 2.52.0
> >
>
> Rest looks good to me!
>
next prev parent reply other threads:[~2026-05-14 2:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 10:41 [PATCH v6 0/3] mm/swap: use swap_ops to register swap device's methods Baoquan He
2026-05-12 10:41 ` [PATCH v6 1/3] mm/swap: rename mm/page_io.c to mm/swap_io.c Baoquan He
2026-05-13 0:27 ` Chris Li
2026-05-13 5:21 ` Christoph Hellwig
2026-05-13 7:10 ` Baoquan He
2026-05-12 10:42 ` [PATCH v6 2/3] mm/swap: use swap_ops to register swap device's methods Baoquan He
2026-05-12 17:53 ` Kairui Song
2026-05-14 2:06 ` Baoquan He [this message]
2026-05-14 6:41 ` Kairui Song
2026-05-14 8:40 ` Baoquan He
2026-05-13 5:32 ` Christoph Hellwig
2026-05-13 15:33 ` Baoquan He
2026-05-13 5:45 ` Christoph Hellwig
2026-05-13 15:38 ` Baoquan He
2026-05-12 10:42 ` [PATCH v6 3/3] mm/swap_io.c: rename swap_writepage_* to swap_write_folio_* Baoquan He
2026-05-12 17:54 ` Kairui Song
2026-05-13 0:31 ` Chris Li
2026-05-13 5:36 ` Christoph Hellwig
2026-05-13 15:44 ` 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=agUuEizORebR3A0O@MiWiFi-R3L-srv \
--to=baoquan.he@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=chrisl@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=ryncsn@gmail.com \
--cc=shikemeng@huaweicloud.com \
--cc=usama.arif@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