[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ef7cec58-9347-46ac-9e1e-e49125940596@oracle.com>
Date: Wed, 7 May 2025 16:14:50 +0100
From: John Garry <john.g.garry@...cle.com>
To: brauner@...nel.org, djwong@...nel.org, hch@....de, viro@...iv.linux.org.uk,
jack@...e.cz, cem@...nel.org
Cc: linux-fsdevel@...r.kernel.org, dchinner@...hat.com,
linux-xfs@...r.kernel.org, linux-kernel@...r.kernel.org,
ojaswin@...ux.ibm.com, ritesh.list@...il.com,
martin.petersen@...cle.com, linux-ext4@...r.kernel.org,
linux-block@...r.kernel.org, catherine.hoang@...cle.com,
linux-api@...r.kernel.org
Subject: Re: [PATCH v12 17/17] xfs: allow sysadmins to specify a maximum
atomic write limit at mount time
On 06/05/2025 10:04, John Garry wrote:
> From: "Darrick J. Wong"<djwong@...nel.org>
>
> Introduce a mount option to allow sysadmins to specify the maximum size
> of an atomic write. If the filesystem can work with the supplied value,
> that becomes the new guaranteed maximum.
>
> The value mustn't be too big for the existing filesystem geometry (max
> write size, max AG/rtgroup size). We dynamically recompute the
> tr_atomic_write transaction reservation based on the given block size,
> check that the current log size isn't less than the new minimum log size
> constraints, and set a new maximum.
>
> The actual software atomic write max is still computed based off of
> tr_atomic_ioend the same way it has for the past few commits. Note also
> that xfs_calc_atomic_write_log_geometry is non-static because mkfs will
> need that.
>
> Signed-off-by: Darrick J. Wong<djwong@...nel.org>
> Signed-off-by: John Garry<john.g.garry@...cle.com>
Reviewed-by: John Garry <john.g.garry@...cle.com>
Powered by blists - more mailing lists