[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ad7ebace-9146-4824-85fb-d65416ad8895@linux.alibaba.com>
Date: Thu, 4 Apr 2024 08:43:31 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: Sweet Tea Dorminy <sweettea-kernel@...miny.me>,
Jonathan Corbet <corbet@....net>, Kent Overstreet
<kent.overstreet@...ux.dev>, Brian Foster <bfoster@...hat.com>,
Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>, Jaegeuk Kim <jaegeuk@...nel.org>,
Chao Yu <chao@...nel.org>, Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>, Jan Kara <jack@...e.cz>,
Mickaël Salaün <mic@...ikod.net>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-bcachefs@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, linux-fsdevel@...r.kernel.org,
kernel-team@...a.com
Subject: Re: [PATCH v3 00/13] fiemap extension for more physical information
Hi,
On 2024/4/3 23:11, Sweet Tea Dorminy wrote:
>
>>
>> I'm not sure why here iomap was excluded technically or I'm missing some
>> previous comments?
>>
>>
>> Could you also make iomap support new FIEMAP physical extent information?
>> since compressed EROFS uses iomap FIEMAP interface to report compressed
>> extents ("z_erofs_iomap_report_ops") but there is no way to return
>> correct compressed lengths, that is unexpected.
>>
>
> I'll add iomap support in v4, I'd skipped it since I was worried it'd be an expansive additional part not necessary initially. Thank you for noting it!
Thanks, I think just fiemap report for iomap seems straight-forward.
Thanks for your work!
Thanks,
Gao Xiang
>
> Sweet Tea
Powered by blists - more mailing lists