[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210225073525.GA3448@lst.de>
Date: Thu, 25 Feb 2021 08:35:25 +0100
From: Christoph Hellwig <hch@....de>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: Ruan Shiyang <ruansy.fnst@...fujitsu.com>,
Christoph Hellwig <hch@....de>, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-nvdimm@...ts.01.org,
linux-fsdevel@...r.kernel.org, darrick.wong@...cle.com,
dan.j.williams@...el.com, willy@...radead.org, jack@...e.cz,
viro@...iv.linux.org.uk, linux-btrfs@...r.kernel.org,
ocfs2-devel@....oracle.com, david@...morbit.com, rgoldwyn@...e.de,
Goldwyn Rodrigues <rgoldwyn@...e.com>
Subject: Re: [PATCH 5/7] fsdax: Dedup file range to use a compare function
On Thu, Feb 18, 2021 at 08:20:18AM -0800, Darrick J. Wong wrote:
> > I think a nested call like this is necessary. That's why I use the open
> > code way.
>
> This might be a good place to implement an iomap_apply2() loop that
> actually /does/ walk all the extents of file1 and file2. There's now
> two users of this idiom.
Why do we need a special helper for that?
> (Possibly structured as a "get next mappings from both" generator
> function like Matthew Wilcox keeps asking for. :))
OTOH this might be a good first use for that.
Powered by blists - more mailing lists