From: Dave Jiang <dave.jiang@intel.com>
To: Alison Schofield <alison.schofield@intel.com>, nvdimm@lists.linux.dev
Subject: Re: [ndctl PATCH 3/3] test/mmap.sh: reduce fallocate size from 1GiB to 256MiB
Date: Wed, 8 Apr 2026 13:18:56 -0700 [thread overview]
Message-ID: <cade917d-637a-4a6f-bcbc-e258dbee3b67@intel.com> (raw)
In-Reply-To: <2b2e0fe8-d163-43f3-b1b7-71d134b86fb7@intel.com>
On 4/1/26 3:53 PM, Dave Jiang wrote:
>
>
> On 3/31/26 9:49 PM, Alison Schofield wrote:
>> The mmap test allocates a 1 GiB file and exercises a matrix of mmap
>> flag combinations across ext4+dax and xfs+dax, performing multiple
>> full-range read and write passes for each case.
>>
>> The coverage of this test comes from the mmap modes and access
>> patterns it exercises (MAP_SHARED vs MAP_PRIVATE, MAP_POPULATE,
>> mlock/munlock, and read-only mappings), not from the size of the
>> mapping itself. These behaviors are not size-dependent, and no test
>> assertions rely on a 1 GiB mapping.
>>
>> Long CI runtimes prompted a closer look at this test, but the
>> reduction stands on its own merits: a 256 MiB mapping still spans many
>> PMD (2 MiB) DAX mappings and exercises the same access patterns, while
>> avoiding unnecessary work in each test case.
>
> No excercise of tests against 1GB page?
>
> DJ
Looking a bit more, fallocate() does not care about underneath page size. So this is probably ok.
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
>
>
>>
>> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
>> ---
>> test/mmap.sh | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/test/mmap.sh b/test/mmap.sh
>> index 7d0053da0e1a..c517d5b0f50b 100755
>> --- a/test/mmap.sh
>> +++ b/test/mmap.sh
>> @@ -59,12 +59,12 @@ rc=1
>>
>> mkfs.ext4 $DEV
>> mount $DEV $MNT -o dax
>> -fallocate -l 1GiB $MNT/$FILE
>> +fallocate -l 256MiB $MNT/$FILE
>> test_mmap
>> umount $MNT
>>
>> mkfs.xfs -f $DEV -m reflink=0
>> mount $DEV $MNT -o dax
>> -fallocate -l 1GiB $MNT/$FILE
>> +fallocate -l 256MiB $MNT/$FILE
>> test_mmap
>> umount $MNT
>
>
next prev parent reply other threads:[~2026-04-08 20:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-01 4:49 [ndctl PATCH 1/3] test/mmap.c: check mmap() result against MAP_FAILED Alison Schofield
2026-04-01 4:49 ` [ndctl PATCH 2/3] test/mmap: move detailed tracing behind -v option Alison Schofield
2026-04-01 22:50 ` Dave Jiang
2026-04-01 4:49 ` [ndctl PATCH 3/3] test/mmap.sh: reduce fallocate size from 1GiB to 256MiB Alison Schofield
2026-04-01 22:53 ` Dave Jiang
2026-04-02 2:59 ` Alison Schofield
2026-04-08 20:18 ` Dave Jiang [this message]
2026-04-01 22:48 ` [ndctl PATCH 1/3] test/mmap.c: check mmap() result against MAP_FAILED Dave Jiang
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=cade917d-637a-4a6f-bcbc-e258dbee3b67@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=nvdimm@lists.linux.dev \
/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