[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251113055758.GA29014@lst.de>
Date: Thu, 13 Nov 2025 06:57:58 +0100
From: Christoph Hellwig <hch@....de>
To: Ritesh Harjani <ritesh.list@...il.com>
Cc: Christoph Hellwig <hch@....de>, Dave Chinner <david@...morbit.com>,
Ojaswin Mujoo <ojaswin@...ux.ibm.com>,
Christian Brauner <brauner@...nel.org>, djwong@...nel.org,
john.g.garry@...cle.com, 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 Thu, Nov 13, 2025 at 11:12:49AM +0530, Ritesh Harjani wrote:
> For e.g. https://lwn.net/Articles/974578/ goes in depth and talks about
> Postgres folks looking for this, since PostgreSQL databases uses
> buffered I/O for their database writes.
Honestly, a database stubbornly using the wrong I/O path should not be
a reaѕon for adding this complexity.
Powered by blists - more mailing lists