[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171206235829.GA28086@linux.intel.com>
Date: Wed, 6 Dec 2017 16:58:29 -0700
From: Ross Zwisler <ross.zwisler@...ux.intel.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Matthew Wilcox <mawilcox@...rosoft.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Jens Axboe <axboe@...nel.dk>,
Rehas Sachdeva <aquannie@...il.com>, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net,
linux-nilfs@...r.kernel.org, linux-btrfs@...r.kernel.org,
linux-xfs@...r.kernel.org, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 00/73] XArray version 4
On Tue, Dec 05, 2017 at 04:40:46PM -0800, Matthew Wilcox wrote:
> From: Matthew Wilcox <mawilcox@...rosoft.com>
>
> I looked through some notes and decided this was version 4 of the XArray.
> Last posted two weeks ago, this version includes a *lot* of changes.
> I'd like to thank Dave Chinner for his feedback, encouragement and
> distracting ideas for improvement, which I'll get to once this is merged.
>
> Highlights:
> - Over 2000 words of documentation in patch 8! And lots more kernel-doc.
> - The page cache is now fully converted to the XArray.
> - Many more tests in the test-suite.
>
> This patch set is not for applying. 0day is still reporting problems,
> and I'd feel bad for eating someone's data. These patches apply on top
> of a set of prepatory patches which just aren't interesting. If you
> want to see the patches applied to a tree, I suggest pulling my git tree:
> http://git.infradead.org/users/willy/linux-dax.git/shortlog/refs/heads/xarray-2017-12-04
> I also left out the idr_preload removals. They're still in the git tree,
> but I'm not looking for feedback on them.
Hey Matthew,
Maybe I missed this from a previous version, but can you explain the
motivation for replacing the radix tree with an xarray? (I think this should
probably still be part of the cover letter?) Do we have a performance problem
we need to solve? A code complexity issue we need to solve? Something else?
- Ross
Powered by blists - more mailing lists