From: Jens Axboe <axboe@kernel.dk>
To: John Garry <john.g.garry@oracle.com>, fio@vger.kernel.org
Cc: martin.petersen@oracle.com, djwong@kernel.org, mcgrof@kernel.org
Subject: Re: [PATCH 1/7] os-linux: Renumber RWF_UNCACHED
Date: Thu, 29 Aug 2024 07:16:30 -0600 [thread overview]
Message-ID: <b761e02d-8c75-4b48-af09-67fb2ca86b4b@kernel.dk> (raw)
In-Reply-To: <20240829123107.520005-2-john.g.garry@oracle.com>
On 8/29/24 6:31 AM, John Garry wrote:
> This now conflicts with RWF_ATOMIC.
Still plan on resurrecting that at some point, but I think
for now we should just drop it. Let me commit something
for that...
--
Jens Axboe
next prev parent reply other threads:[~2024-08-29 13:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 12:31 [PATCH 0/7] fio: atomic write support John Garry
2024-08-29 12:31 ` [PATCH 1/7] os-linux: Renumber RWF_UNCACHED John Garry
2024-08-29 13:16 ` Jens Axboe [this message]
2024-08-29 12:31 ` [PATCH 2/7] os-linux: Define RWF_ATOMIC John Garry
2024-08-29 12:31 ` [PATCH 3/7] os: Reintroduce atomic write support John Garry
2024-08-29 12:31 ` [PATCH 4/7] verify: Ignore sequence number errors for atomic writes John Garry
2024-08-29 12:31 ` [PATCH 5/7] pvsync2: Support RWF_ATOMIC John Garry
2024-08-29 12:31 ` [PATCH 6/7] libaio: " John Garry
2024-08-29 12:31 ` [PATCH 7/7] io_uring: " John Garry
2024-09-05 9:37 ` [PATCH 0/7] fio: atomic write support Luis Chamberlain
2024-09-06 15:22 ` John Garry
2024-09-06 23:29 ` Luis Chamberlain
2024-09-09 8:12 ` John Garry
2024-09-09 19:48 ` Jens Axboe
2024-09-09 20:20 ` John Garry
2024-09-09 21:03 ` Luis Chamberlain
2024-09-09 19:53 ` Jens Axboe
2024-09-09 20:28 ` John Garry
2024-09-10 1:01 ` Jens Axboe
2024-09-10 10:03 ` John Garry
2024-09-10 15:56 ` Jens Axboe
2024-09-10 16:38 ` John Garry
2024-09-10 16:56 ` Jens Axboe
2024-09-10 17:17 ` John Garry
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=b761e02d-8c75-4b48-af09-67fb2ca86b4b@kernel.dk \
--to=axboe@kernel.dk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.