[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160910074228.GA23749@infradead.org>
Date: Sat, 10 Sep 2016 00:42:28 -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:33:18AM +0000, Matthew Wilcox wrote:
> > caller specific is unaceptable. That being said your idea doesn't sounds
> > unreasonable, but will require a bit more work and has no real short-term
> > need.
>
> So your proposal is to remove buffer_heads from ext2?
No, the proposal is to remove buffer_heads from XFS first, then GFS2
and then maybe others like ext4. I'd like to remove buffer_heads from
the DAX path for ext2 and ext4 entitrely for sure (and direct I/O next).
Powered by blists - more mailing lists