[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160911124741.GA746@infradead.org>
Date: Sun, 11 Sep 2016 05:47:41 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Matthew Wilcox <mawilcox@...rosoft.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
Theodore Ts'o <tytso@....edu>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-nvdimm@...1.01.org" <linux-nvdimm@...1.01.org>,
Dave Chinner <david@...morbit.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Alexander Viro <viro@...iv.linux.org.uk>,
Jan Kara <jack@...e.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH v2 2/9] ext2: tell DAX the size of allocation holes
On Sat, Sep 10, 2016 at 07:52:53AM +0000, Matthew Wilcox wrote:
> DAX code over to using iomap requires converting all of ext2 away from
> buffer_head; are you saying he's wrong?
Not sure if he's really saying that, but it's wrong for sure. Just
to prove that I came up with a working ext2 iomap DAX implementation
in a few hours today. I'll take a stab at ext4 and the block device
as well and will post the updated series early next week - I'll need
to take care of a few high priority todo list items first.
Powered by blists - more mailing lists