[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d645cb5-7589-4544-a547-19729610d44d@oracle.com>
Date: Mon, 17 Nov 2025 10:59:55 +0000
From: John Garry <john.g.garry@...cle.com>
To: Dave Chinner <david@...morbit.com>, Ojaswin Mujoo <ojaswin@...ux.ibm.com>
Cc: Ritesh Harjani <ritesh.list@...il.com>, Christoph Hellwig <hch@....de>,
Christian Brauner <brauner@...nel.org>, djwong@...nel.org,
tytso@....edu, willy@...radead.org, dchinner@...hat.com,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, jack@...e.cz, nilay@...ux.ibm.com,
martin.petersen@...cle.com, rostedt@...dmis.org, axboe@...nel.dk,
linux-block@...r.kernel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/8] xfs: single block atomic writes for buffered IO
On 16/11/2025 08:11, Dave Chinner wrote:
>> This patch set focuses on HW accelerated single block atomic writes with
>> buffered IO, to get some early reviews on the core design.
> What hardware acceleration? Hardware atomic writes are do not make
> IO faster; they only change IO failure semantics in certain corner
> cases.
I think that he references using REQ_ATOMIC-based bio vs xfs
software-based atomic writes (which reuse the CoW infrastructure). And
the former is considerably faster from my testing (for DIO, obvs). But
the latter has not been optimized.
Powered by blists - more mailing lists