[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d7f2c68-bef7-45bd-9572-97ed8e182fc6@oracle.com>
Date: Wed, 23 Apr 2025 09:18:12 +0100
From: John Garry <john.g.garry@...cle.com>
To: Christoph Hellwig <hch@....de>
Cc: brauner@...nel.org, djwong@...nel.org, viro@...iv.linux.org.uk,
jack@...e.cz, cem@...nel.org, 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 v8 10/15] xfs: add large atomic writes checks in
xfs_direct_write_iomap_begin()
On 23/04/2025 09:16, Christoph Hellwig wrote:
> On Tue, Apr 22, 2025 at 12:27:34PM +0000, John Garry wrote:
>> For when large atomic writes (> 1x FS block) are supported, there will be
>> various occasions when HW offload may not be possible.
>>
>> Such instances include:
>> - unaligned extent mapping wrt write length
>> - extent mappings which do not cover the full write, e.g. the write spans
>> sparse or mixed-mapping extents
>> - the write length is greater than HW offload can support
>
> or simply no hardware support at all.
sure, will add
>
> Otherwise looks good:
>
> Reviewed-by: Christoph Hellwig <hch@....de>
cheers
Powered by blists - more mailing lists