From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754363AbcIJHmd (ORCPT ); Sat, 10 Sep 2016 03:42:33 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:45362 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750812AbcIJHmb (ORCPT ); Sat, 10 Sep 2016 03:42:31 -0400 Date: Sat, 10 Sep 2016 00:42:28 -0700 From: Christoph Hellwig To: Matthew Wilcox Cc: Christoph Hellwig , Ross Zwisler , "Theodore Ts'o" , "linux-kernel@vger.kernel.org" , Andrew Morton , "linux-nvdimm@ml01.01.org" , Dave Chinner , "linux-mm@kvack.org" , Andreas Dilger , Alexander Viro , Jan Kara , "linux-fsdevel@vger.kernel.org" , "linux-ext4@vger.kernel.org" Subject: Re: [PATCH v2 2/9] ext2: tell DAX the size of allocation holes Message-ID: <20160910074228.GA23749@infradead.org> References: <20160823220419.11717-1-ross.zwisler@linux.intel.com> <20160823220419.11717-3-ross.zwisler@linux.intel.com> <20160825075728.GA11235@infradead.org> <20160826212934.GA11265@linux.intel.com> <20160829074116.GA16491@infradead.org> <20160829125741.cdnbb2uaditcmnw2@thunk.org> <20160909164808.GC18554@linux.intel.com> <20160910073012.GA5295@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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).