From: Jens Axboe <axboe@kernel.dk>
To: fio@vger.kernel.org, John Garry <john.g.garry@oracle.com>
Cc: martin.petersen@oracle.com, djwong@kernel.org, mcgrof@kernel.org,
alan.adamson@oracle.com, david@fromorbit.com
Subject: Re: [PATCH v2 0/9] fio: atomic write support
Date: Mon, 16 Sep 2024 20:23:25 -0600 [thread overview]
Message-ID: <172653980552.75199.7258206217332889604.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240916165347.2226763-1-john.g.garry@oracle.com>
On Mon, 16 Sep 2024 16:53:38 +0000, John Garry wrote:
> This series re-introduces atomic write support.
>
> Some time ago support was added for O_ATOMIC in fio, but O_ATOMIC support
> never made it into the linux kernel, so fio support was dropped. However
> some plumbing was left behind; specifically, we can still pass command
> line arg --atomic=1, which sets thread option oatomic, but that is just
> ignored.
>
> [...]
Applied, thanks!
[1/9] os-linux: Define RWF_ATOMIC
commit: 5ba34480dc222db47d7813009eb95a7543790dd3
[2/9] os: Reintroduce atomic write support
commit: 40f1fc11d4fc6dbbd3c0eb5852e24126dad5fd4e
[3/9] pvsync2: Support RWF_ATOMIC
commit: 80226c53d994e8a9206ed7acf4a4dc75a8691792
[4/9] libaio: Support RWF_ATOMIC
commit: a79319fe6efd138ae346aff28b528682fbed0a7c
[5/9] io_uring: Support RWF_ATOMIC
commit: b1552b6e655dba1b1d4957c04a19361654ab38ad
[6/9] tools/fiograph: Update for atomic support
commit: 274a69eab08837e4e32185f2944e3b98dd5258c0
[7/9] doc: Document atomic command
commit: cd3de3d7700294f28d52cc781d1ce3982c12ba7e
[8/9] fio: Support verify_write_sequence
commit: 2dd80ee4598bcd69d1413fd2f1205cbffb56d787
[9/9] examples: Add example for atomic write verify
commit: f23208c8860de515f025af6ac34d6a227f277e67
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-09-17 2:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-16 16:53 [PATCH v2 0/9] fio: atomic write support John Garry
2024-09-16 16:53 ` [PATCH v2 1/9] os-linux: Define RWF_ATOMIC John Garry
2024-09-16 16:53 ` [PATCH v2 2/9] os: Reintroduce atomic write support John Garry
2024-09-16 16:53 ` [PATCH v2 3/9] pvsync2: Support RWF_ATOMIC John Garry
2024-09-16 16:53 ` [PATCH v2 4/9] libaio: " John Garry
2024-09-16 16:53 ` [PATCH v2 5/9] io_uring: " John Garry
2024-09-16 16:53 ` [PATCH v2 6/9] tools/fiograph: Update for atomic support John Garry
2024-09-16 16:53 ` [PATCH v2 7/9] doc: Document atomic command John Garry
2024-09-16 16:53 ` [PATCH v2 8/9] fio: Support verify_write_sequence John Garry
2024-09-16 16:53 ` [PATCH v2 9/9] examples: Add example for atomic write verify John Garry
2024-09-17 2:23 ` Jens Axboe [this message]
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=172653980552.75199.7258206217332889604.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=alan.adamson@oracle.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=fio@vger.kernel.org \
--cc=john.g.garry@oracle.com \
--cc=martin.petersen@oracle.com \
--cc=mcgrof@kernel.org \
/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