From: Andrew Morton <akpm@linux-foundation.org>
To: "Yijia Wang" <wangyijia.yeah@bytedance.com>
Cc: "Shuah Khan" <shuah@kernel.org>,
<linux-kselftest@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, "Muchun Song" <muchun.song@linux.dev>
Subject: Re: [PATCH RESEND v3] selftests: mincore: fix the readahead check on large base page sizes
Date: Sat, 4 Jul 2026 20:36:16 -0700 [thread overview]
Message-ID: <20260704203616.1ce10365e07c746f1e805cab@linux-foundation.org> (raw)
In-Reply-To: <20260703125253.3016281-1-wangyijia.yeah@bytedance.com>
On Fri, 3 Jul 2026 20:52:53 +0800 "Yijia Wang" <wangyijia.yeah@bytedance.com> wrote:
> check_file_mmap faults a page in the middle of a file mapping and
> expects the readahead window to have populated further pages *after*
> it. With a large base page size this is wrong and the test fails
> reliably, e.g. on arm64 with 64K pages:
>
> # mincore_selftest.c:260:check_file_mmap:Expected ra_pages (0) > 0 (0)
> # mincore_selftest.c:261:check_file_mmap:No read-ahead pages found in memory
> not ok 4 global.check_file_mmap
I'm not sure this is a good thing for us to be self-testing for. It's
poking pretty deeply inside the internal implementations of
kernel-of-the-moment.
Oh well, I guss if the test suddenly starts reporting errors, it might
be something we want to look into.
> The read-around window is read_ahead_kb / page_size pages wide and is
> centred on the faulting page (mm/filemap.c):
>
> ra->start = max(0, pgoff - ra_pages / 2)
>
> With the default 128K budget that is 32 pages on 4K but only 2 pages on
> 64K, so the window becomes [pgoff-1, pgoff] and the single extra page
> lands *before* the faulted page. The forward-only scan finds nothing.
> This is not a huge-page (THP) effect; it is just a byte-sized readahead
> budget divided by a large page size plus a fault-centred window.
>
> Count readahead pages on both sides of the faulted page, and skip the
> readahead check up front when there is no usable read-around window:
> either it is narrower than two pages (readahead disabled, or the base
> page size so large that read_ahead_kb covers a single page), or the file
> has no backing block device whose read_ahead_kb can be read (e.g. on
> tmpfs). When the window is wide enough the EXPECT_GT(ra_pages, 0)
> assertion is kept, so a kernel that should read ahead but does not is
> still caught.
Thanks. AI review might have found a couple of things of interest:
https://sashiko.dev/#/patchset/20260703125253.3016281-1-wangyijia.yeah@bytedance.com
next prev parent reply other threads:[~2026-07-05 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 12:52 [PATCH RESEND v3] selftests: mincore: fix the readahead check on large base page sizes Yijia Wang
2026-07-05 3:36 ` Andrew Morton [this message]
2026-07-07 6:25 ` 王翊嘉
2026-07-07 21:23 ` Andrew Morton
2026-07-08 7:59 ` [PATCH v4] selftests: mincore: count file-mmap readahead on both sides 王翊嘉
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=20260704203616.1ce10365e07c746f1e805cab@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=shuah@kernel.org \
--cc=wangyijia.yeah@bytedance.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