[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z9FCMwZTzpmwsw1W@infradead.org>
Date: Wed, 12 Mar 2025 01:13:39 -0700
From: Christoph Hellwig <hch@...radead.org>
To: John Garry <john.g.garry@...cle.com>
Cc: Christoph Hellwig <hch@...radead.org>, brauner@...nel.org,
djwong@...nel.org, cem@...nel.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
ojaswin@...ux.ibm.com, ritesh.list@...il.com,
martin.petersen@...cle.com
Subject: Re: [PATCH v5 08/10] xfs: Update atomic write max size
On Wed, Mar 12, 2025 at 08:09:47AM +0000, John Garry wrote:
> On 12/03/2025 07:41, Christoph Hellwig wrote:
> > On Mon, Mar 10, 2025 at 06:39:44PM +0000, John Garry wrote:
> > > For RT inode, just limit to 1x block, even though larger can be supported
> > > in future.
> >
> > Why?
>
> Adding RT support adds even more complexity upfront, and RT is uncommonly
> used.
>
> In addition, it will be limited to using power-of-2 rtextsize, so a slightly
> restricted feature.
Please spell that out in the commit message.
Powered by blists - more mailing lists