From: David CARLIER <devnexen@gmail.com>
To: Barry Song <21cnbao@gmail.com>
Cc: David Hildenbrand <david@kernel.org>,
Kairui Song <kasong@tencent.com>, Chris Li <chrisl@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kemeng Shi <shikemeng@huaweicloud.com>,
Nhat Pham <nphamcs@gmail.com>, Baoquan He <bhe@redhat.com>,
Youngjun Park <youngjun.park@lge.com>,
NeilBrown <neil@brown.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2] mm/page_io: fix PSWPIN undercount for large folios in sio_read_complete()
Date: Wed, 1 Apr 2026 08:10:08 +0100 [thread overview]
Message-ID: <CA+XhMqw59iWLPQba5WSaF5Y7HKDgf3BjjBLn_X=w=g5tAk26-Q@mail.gmail.com> (raw)
In-Reply-To: <CAGsJ_4zpre2gUcYdZxY3s57=ESf_av59L+DNCYd0hZ3UtHNvSw@mail.gmail.com>
On Tue, 31 Mar 2026 at 23:33, Barry Song <21cnbao@gmail.com> wrote:
>
> On Mon, Mar 30, 2026 at 3:12 PM David Carlier <devnexen@gmail.com> wrote:
> >
> > sio_read_complete() uses sio->pages to account global PSWPIN vm events,
> > but sio->pages tracks the number of bvec entries (folios), not base
> > pages. For large folios this undercounts compared to the per-memcg path
> > which correctly uses folio_nr_pages(), and compared to the bdev read
> > paths which also use folio_nr_pages().
> >
> > Use sio->len >> PAGE_SHIFT instead, which gives the correct base page
> > count since sio->len is accumulated via folio_size(folio).
> >
> > Fixes: a1a0dfd56f97 ("mm: handle THP in swap_*page_fs()")
> > Signed-off-by: David Carlier <devnexen@gmail.com>
>
> The patch seems theoretically correct, but I’m wondering
> where we can swap in mTHP for filesystem-based swap?
>
> In both do_swap_page() and shmem_swapin_folio(), we check
> data_race(si->flags & SWP_SYNCHRONOUS_IO) before allocating
> large folios. Am I missing something?
▎ The patch seems theoretically correct, but I'm wondering
▎ where we can swap in mTHP for filesystem-based swap?
▎ In both do_swap_page() and shmem_swapin_folio(), we check
▎ data_race(si->flags & SWP_SYNCHRONOUS_IO) before allocating
▎ large folios. Am I missing something?
You're right, I missed that. SWP_FS_OPS is only set by NFS and
SMB which have no bdev, so SWP_SYNCHRONOUS_IO can never be set
alongside it. Large folios can't currently reach this path since
both do_swap_page() and shmem_swapin_folio() gate mTHP allocation
on SWP_SYNCHRONOUS_IO.
That said, sio_read_complete() already calls count_mthp_stat()
and the per-memcg accounting uses folio_nr_pages(), so the code
seems written with large folios in mind even if the path is
currently unreachable. Using sio->pages (bvec entry count) for
a base-page count is still semantically wrong, but I understand
the practical impact is nil today.
Happy to either drop this or keep it as a correctness cleanup,
whatever you and Andrew prefer.
Cheers !
>
> > ---
> > mm/page_io.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/page_io.c b/mm/page_io.c
> > index 63b262f4c5a9..1389cd57ca88 100644
> > --- a/mm/page_io.c
> > +++ b/mm/page_io.c
> > @@ -497,7 +497,7 @@ static void sio_read_complete(struct kiocb *iocb, long ret)
> > folio_mark_uptodate(folio);
> > folio_unlock(folio);
> > }
> > - count_vm_events(PSWPIN, sio->pages);
> > + count_vm_events(PSWPIN, sio->len >> PAGE_SHIFT);
> > } else {
> > for (p = 0; p < sio->pages; p++) {
> > struct folio *folio = page_folio(sio->bvec[p].bv_page);
> > --
> > 2.53.0
> >
>
> Thanks
> Barry
next prev parent reply other threads:[~2026-04-01 7:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 7:12 David Carlier
2026-03-30 22:20 ` Andrew Morton
2026-03-31 22:33 ` Barry Song
2026-04-01 7:10 ` David CARLIER [this message]
2026-04-01 7:30 ` David Hildenbrand (Arm)
2026-04-01 20:22 ` Barry Song
2026-04-01 7:47 ` [PATCH v3] mm/page_io: use sio->len for PSWPIN accounting " David Carlier
2026-04-01 8:32 ` David Hildenbrand (Arm)
2026-04-01 22:58 ` Andrew Morton
2026-04-01 23:43 ` Barry Song
2026-04-02 3:07 ` Chris Li
2026-04-02 4:11 ` Matthew Wilcox
2026-04-02 5:51 ` Barry Song
2026-04-02 6:01 ` David CARLIER
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='CA+XhMqw59iWLPQba5WSaF5Y7HKDgf3BjjBLn_X=w=g5tAk26-Q@mail.gmail.com' \
--to=devnexen@gmail.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=chrisl@kernel.org \
--cc=david@kernel.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=neil@brown.name \
--cc=nphamcs@gmail.com \
--cc=shikemeng@huaweicloud.com \
--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