All of lore.kernel.org
 help / color / mirror / Atom feed
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 0/7] fio: atomic write support
Date: Mon, 9 Sep 2024 19:01:02 -0600	[thread overview]
Message-ID: <f689c9ea-b677-4521-8363-1c4f2f3c81f0@kernel.dk> (raw)
In-Reply-To: <1185aac7-de61-4071-83fe-802b52e458e2@oracle.com>

On 9/9/24 2:28 PM, John Garry wrote:
> On 09/09/2024 20:53, Jens Axboe wrote:
>> John,
>>
>> Maybe it wasn't clear, but I committed that change I mentioned in my
>> initial reply basically right after.
> 
> Thanks for doing that.
> 
>> If you could send a v2 on top of
>> the current tree, that'd be great.
> 
> I was preparing a v2 the same as this, but do you think that I should
> just add a new verify option for atomic writes to ignore the header?
> Or is just saying "you have selected atomic=1, so I'll just ignore the
> header for you" ok?

I'm still not following why atomic writes make this any different. They
should not. If you have multiple writers writing the same blocks, yeah
you will get verification errors. This is true for any kind of write, be
it buffered, dio, or atomic. So unless I'm missing something here, I'd
just drop that patch.

-- 
Jens Axboe

  reply	other threads:[~2024-09-10  1:01 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
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 [this message]
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=f689c9ea-b677-4521-8363-1c4f2f3c81f0@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.