xfs
[Top] [All Lists]

Re: [PATCH 11/47] xfs: move deferred operations into a separate file

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: [PATCH 11/47] xfs: move deferred operations into a separate file
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 3 Aug 2016 08:39:50 +1000
Cc: "Darrick J. Wong" <darrick.wong@xxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, vishal.l.verma@xxxxxxxxx, bfoster@xxxxxxxxxx, xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <20160801080223.GB30547@xxxxxxxxxxxxx>
References: <146907695530.25461.3225785294902719773.stgit@xxxxxxxxxxxxxxxx> <146907703710.25461.16650495404061662831.stgit@xxxxxxxxxxxxxxxx> <20160801080223.GB30547@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Mon, Aug 01, 2016 at 01:02:23AM -0700, Christoph Hellwig wrote:
> I looked over this again and I really don't see the use case of merging
> it.  Yes, the freed extent, rmap and reflink code is fairly similar, but
> there is all kinds of subtile differences that we need to paper over using
> methods and flags.  I think we're better off not trying to share this
> code and have a separate, but easily understandable implementation
> for each btree.  At least for the traditional traditional freed extent
> case the new code also is a lot less optimal than the previous version.

Rather than have to make major changes to core infrastructure now,
let's work this out as a separate patchset to clean up the rmap and
reflink code in the next couple of releases. It's going to be better
to get working code out there now under the experimental tag than it
is is to keep it as an out of tree patchset for another cycle.

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>