From: John Garry <john.g.garry@oracle.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>, fstests@vger.kernel.org
Cc: Ritesh Harjani <ritesh.list@gmail.com>, djwong@kernel.org
Subject: Re: [RFC 10/12] ext4/062: Atomic writes test for bigalloc using fio crc verifier on multiple files
Date: Thu, 12 Jun 2025 11:26:17 +0100 [thread overview]
Message-ID: <05005921-517b-4286-be24-eeef625e488f@oracle.com> (raw)
In-Reply-To: <9b0512d4063c2dc421e3e72e8c899460dd0c2644.1749629233.git.ojaswin@linux.ibm.com>
On 11/06/2025 10:34, Ojaswin Mujoo wrote:
> From: "Ritesh Harjani (IBM)"<ritesh.list@gmail.com>
>
> Brute force all possible blocksize clustersize combination on a bigalloc
> filesystem for stressing atomic write using fio data crc verifier. We run
> multiple threads in parallel with each job writing to its own file. The
> parallel jobs running on a constrained filesystem size ensure that we stress
> the ext4 allocator to allocate contiguous extents.
>
> Signed-off-by: Ritesh Harjani (IBM)<ritesh.list@gmail.com>
> Signed-off-by: Ojaswin Mujoo<ojaswin@linux.ibm.com>
RWF_ATOMIC does not guarantee that racing atomic writes and reads are
serialised. That is what you are testing here, right?
NVMe and SCSI do guarantee this (serialisation). However, reads in the
block layer may be split into multiple requests, even though unlikely.
next prev parent reply other threads:[~2025-06-12 10:26 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 9:34 [RFC 00/12] Add more tests for multi fs block atomic writes Ojaswin Mujoo
2025-06-11 9:34 ` [RFC 01/12] common/preamble: Fix fsx for ext4 with bigalloc Ojaswin Mujoo
2025-06-11 14:30 ` Darrick J. Wong
2025-06-12 6:11 ` Ojaswin Mujoo
2025-06-12 14:36 ` Darrick J. Wong
2025-06-13 5:31 ` Ojaswin Mujoo
2025-06-13 15:04 ` Darrick J. Wong
2025-06-17 6:22 ` Ojaswin Mujoo
2025-06-30 15:27 ` Darrick J. Wong
2025-06-18 19:13 ` Zorro Lang
2025-06-20 6:21 ` Ojaswin Mujoo
2025-06-20 9:59 ` Zorro Lang
2025-06-11 9:34 ` [RFC 02/12] common/rc: Add a helper to run fsx on a given file Ojaswin Mujoo
2025-06-11 14:31 ` Darrick J. Wong
2025-06-12 6:17 ` Ojaswin Mujoo
2025-06-12 14:35 ` Darrick J. Wong
2025-06-11 9:34 ` [RFC 03/12] ltp/fsx.c: Add atomic writes support to fsx Ojaswin Mujoo
2025-06-11 14:35 ` Darrick J. Wong
2025-06-12 6:18 ` Ojaswin Mujoo
2025-06-11 9:34 ` [RFC 04/12] generic/767: Add atomic write test using fio crc check verifier Ojaswin Mujoo
2025-06-11 14:42 ` Darrick J. Wong
2025-06-12 6:22 ` Ojaswin Mujoo
2025-06-12 14:55 ` Darrick J. Wong
2025-06-18 19:34 ` Zorro Lang
2025-06-20 7:06 ` Ojaswin Mujoo
2025-06-11 9:34 ` [RFC 05/12] generic/769: Add atomic write test using fio verify on file mixed mappings Ojaswin Mujoo
2025-06-11 15:35 ` Darrick J. Wong
2025-06-11 9:34 ` [RFC 06/12] generic/770: Add atomic write multi-fsblock O_[D]SYNC tests Ojaswin Mujoo
2025-06-11 15:36 ` Darrick J. Wong
2025-06-12 6:23 ` Ojaswin Mujoo
2025-06-18 20:17 ` Zorro Lang
2025-06-20 8:20 ` Ojaswin Mujoo
2025-06-20 12:12 ` Zorro Lang
2025-06-11 9:34 ` [RFC 07/12] generic/771: Stress fsx with atomic writes enabled Ojaswin Mujoo
2025-06-11 14:45 ` Darrick J. Wong
2025-06-12 6:27 ` Ojaswin Mujoo
2025-06-12 15:14 ` Darrick J. Wong
2025-06-13 5:20 ` Ojaswin Mujoo
2025-06-18 20:27 ` Zorro Lang
2025-06-20 8:26 ` Ojaswin Mujoo
2025-06-11 9:34 ` [RFC 08/12] generic/772: Add sudden shutdown tests for multi block atomic writes Ojaswin Mujoo
2025-06-11 15:38 ` Darrick J. Wong
2025-06-12 6:28 ` Ojaswin Mujoo
2025-06-19 7:15 ` Zorro Lang
2025-06-20 11:11 ` Ojaswin Mujoo
2025-06-20 14:05 ` John Garry
2025-06-20 15:24 ` Ojaswin Mujoo
2025-06-11 9:34 ` [RFC 09/12] ext4/061: Atomic writes stress test for bigalloc using fio crc verifier Ojaswin Mujoo
2025-06-19 7:43 ` Zorro Lang
2025-06-20 15:08 ` Ojaswin Mujoo
2025-06-20 16:53 ` Zorro Lang
2025-06-11 9:34 ` [RFC 10/12] ext4/062: Atomic writes test for bigalloc using fio crc verifier on multiple files Ojaswin Mujoo
2025-06-12 10:26 ` John Garry [this message]
2025-06-13 5:37 ` Ojaswin Mujoo
2025-06-20 14:01 ` John Garry
2025-06-20 16:49 ` Ojaswin Mujoo
2025-06-19 7:45 ` Zorro Lang
2025-06-11 9:34 ` [RFC 11/12] ext4/063: Atomic write test for extent split across leaf nodes Ojaswin Mujoo
2025-06-19 7:52 ` Zorro Lang
2025-06-11 9:34 ` [RFC 12/12] ext4/064: Add atomic write tests for journal credit calculation Ojaswin Mujoo
2025-06-19 7:58 ` Zorro Lang
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=05005921-517b-4286-be24-eeef625e488f@oracle.com \
--to=john.g.garry@oracle.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.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