From: John Garry <john.g.garry@oracle.com>
To: "Darrick J. Wong" <djwong@kernel.org>, zlang@redhat.com
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 6/7] generic/774: reduce file size
Date: Tue, 11 Nov 2025 09:13:27 +0000 [thread overview]
Message-ID: <fce01b4e-928a-48c8-afe2-265e5893c6cf@oracle.com> (raw)
In-Reply-To: <176279909116.605950.12144124358096086284.stgit@frogsfrogsfrogs>
On 10/11/2025 18:27, Darrick J. Wong wrote:
> From: Darrick J. Wong <djwong@kernel.org>
>
> We've gotten complaints about this test taking hours to run and
> producing stall warning on test VMs with a large number of cpu cores. I
> think this is due to the maximum atomic write unit being very large on
> XFS where we can fall back to a software-based out of place write
> implementation.
>
> On the victim machine, the atomic write max is 4MB and there are 24
> CPUs. As a result, aw_bsize to be 1MB, so the file size is
> 1MB * 24 * 2 * 100 == 4.8GB. I set up a test machine with fast storage
> and 24 CPUs, and the atomic writes poked along at 25MB/s and the total
> runtime was 300s. On spinning rust those stats will be much worse.
>
> Let's try backing the file size off by 10x and see if that eases the
> complaints.
>
The awu max for xfs is still unbounded (so the file size could still be
huge). For ext4, it is limited by HW constraints - the largest HW awu
max I heard about is 256KB. How about also limiting awu max to something
sane, like 1MB?
> Cc: <fstests@vger.kernel.org> # v2025.10.20
> Fixes: 9117fb93b41c38 ("generic: Add atomic write test using fio verify on file mixed mappings")
> Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> ---
> tests/generic/774 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> diff --git a/tests/generic/774 b/tests/generic/774
> index 7a4d70167f9959..28886ed5b09ff7 100755
> --- a/tests/generic/774
> +++ b/tests/generic/774
> @@ -29,7 +29,7 @@ aw_bsize=$(_max "$awu_min_write" "$((awu_max_write/4))")
> fsbsize=$(_get_block_size $SCRATCH_MNT)
>
> threads=$(_min "$(($(nproc) * 2 * LOAD_FACTOR))" "100")
> -filesize=$((aw_bsize * threads * 100))
> +filesize=$((aw_bsize * threads * 10))
> depth=$threads
> aw_io_size=$((filesize / threads))
> aw_io_inc=$aw_io_size
>
next prev parent reply other threads:[~2025-11-11 9:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 18:26 [PATCHSET] fstests: more random fixes for v2025.11.04 Darrick J. Wong
2025-11-10 18:26 ` [PATCH 1/7] common: leave any breadcrumbs when _link_out_file_named can't find the output file Darrick J. Wong
2025-11-11 9:13 ` Christoph Hellwig
2025-11-10 18:26 ` [PATCH 2/7] generic/778: fix severe performance problems Darrick J. Wong
2025-11-11 9:27 ` Christoph Hellwig
2025-11-13 11:53 ` Ojaswin Mujoo
2025-11-15 2:32 ` Darrick J. Wong
2025-11-29 8:52 ` Ojaswin Mujoo
2025-12-01 23:19 ` Darrick J. Wong
2025-12-03 6:19 ` Ojaswin Mujoo
2025-12-04 17:18 ` Darrick J. Wong
2025-11-10 18:26 ` [PATCH 3/7] generic/778: fix background loop control with sentinel files Darrick J. Wong
2025-11-11 9:28 ` Christoph Hellwig
2025-11-13 11:06 ` Ojaswin Mujoo
2025-11-10 18:27 ` [PATCH 4/7] generic/019: skip test when there is no journal Darrick J. Wong
2025-11-11 9:28 ` Christoph Hellwig
2025-11-12 18:20 ` Darrick J. Wong
2025-11-10 18:27 ` [PATCH 5/7] xfs/837: fix test to work with pre-metadir quota mount options Darrick J. Wong
2025-11-11 9:29 ` Christoph Hellwig
2025-11-10 18:27 ` [PATCH 6/7] generic/774: reduce file size Darrick J. Wong
2025-11-11 9:13 ` John Garry [this message]
2025-11-11 9:29 ` Christoph Hellwig
2025-11-11 9:31 ` Christoph Hellwig
2025-11-12 18:05 ` Darrick J. Wong
2025-11-13 10:44 ` Ojaswin Mujoo
2025-11-10 18:27 ` [PATCH 7/7] generic/774: turn off lfsr Darrick J. Wong
2025-11-11 9:01 ` John Garry
2025-11-12 18:15 ` Darrick J. Wong
2025-11-11 9:32 ` Christoph Hellwig
2025-11-13 10:34 ` Ojaswin Mujoo
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=fce01b4e-928a-48c8-afe2-265e5893c6cf@oracle.com \
--to=john.g.garry@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=zlang@redhat.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