From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH v2 2/9] ext2: tell DAX the size of allocation holes Date: Sat, 10 Sep 2016 07:56:43 -0700 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: Sender: owner-linux-mm@kvack.org To: Matthew Wilcox Cc: Ross Zwisler , Theodore Ts'o , Christoph Hellwig , "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" List-Id: linux-nvdimm@lists.01.org On Sat, Sep 10, 2016 at 1:15 AM, Matthew Wilcox wrote: > From: Dan Williams [mailto:dan.j.williams@intel.com] >> /me grumbles about top-posting... > > Let's see if this does any better .. there's lots of new features, but I don't see a 'wrap lines at 80 columns' option. Unfortunately. Much appreciated. [..] >> So the current dax implementation is still struggling to get right (pmd faulting, >> dirty entry cleaning, etc) and this seems like a rewrite that sets us up for future >> features without addressing the current bugs and todo items. In comparison >> the iomap conversion work seems incremental and conserving of current >> development momentum. > > I believe your assessment is incorrect. If converting the current DAX code to > use iomap forces converting ext2, then it's time to get rid of all the half-measures > currently in place. You left off one todo item that this does get us a step closer to > fixing -- support for DMA to mmaped DAX files. I didn't leave that off, DMA is solved with devm_memremap_pages(). Now, DMA without the ~1.6% capacity tax for the memmap array is interesting, but that's a new feature. > I think it also puts us in a better > position to fix the 2MB support, locking, and dirtiness tracking. Oh, and it does > fix the multivolume support (because the sectors in the radix tree could be > interpreted as being from the wrong volume). > >> I agree with you that continuing to touch ext2 is not a good idea, but I'm not >> yet convinced that now is the time to go do dax-2.0 when we haven't finished >> shipping dax-1.0. > > dax-1.0 died long ago ... I think we're up to at least DAX version 4 by now. My point is that I want to address the current slate of problems before solving new questions like "how do we support non-block based filesystems?". We just happened to land DAX in the middle of the in-progress buffer_head removal effort, so DAX should not stand in the way of where filesystems were already going. I'm arguing to complete all the false starts and half measures that are presently in DAX and then look to incrementally evolve the interfaces to something new without regressing any of it. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754888AbcIJO4r (ORCPT ); Sat, 10 Sep 2016 10:56:47 -0400 Received: from mail-oi0-f41.google.com ([209.85.218.41]:33899 "EHLO mail-oi0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754419AbcIJO4p (ORCPT ); Sat, 10 Sep 2016 10:56:45 -0400 MIME-Version: 1.0 In-Reply-To: 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> From: Dan Williams Date: Sat, 10 Sep 2016 07:56:43 -0700 Message-ID: Subject: Re: [PATCH v2 2/9] ext2: tell DAX the size of allocation holes To: Matthew Wilcox Cc: Ross Zwisler , "Theodore Ts'o" , Christoph Hellwig , "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" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Sep 10, 2016 at 1:15 AM, Matthew Wilcox wrote: > From: Dan Williams [mailto:dan.j.williams@intel.com] >> /me grumbles about top-posting... > > Let's see if this does any better .. there's lots of new features, but I don't see a 'wrap lines at 80 columns' option. Unfortunately. Much appreciated. [..] >> So the current dax implementation is still struggling to get right (pmd faulting, >> dirty entry cleaning, etc) and this seems like a rewrite that sets us up for future >> features without addressing the current bugs and todo items. In comparison >> the iomap conversion work seems incremental and conserving of current >> development momentum. > > I believe your assessment is incorrect. If converting the current DAX code to > use iomap forces converting ext2, then it's time to get rid of all the half-measures > currently in place. You left off one todo item that this does get us a step closer to > fixing -- support for DMA to mmaped DAX files. I didn't leave that off, DMA is solved with devm_memremap_pages(). Now, DMA without the ~1.6% capacity tax for the memmap array is interesting, but that's a new feature. > I think it also puts us in a better > position to fix the 2MB support, locking, and dirtiness tracking. Oh, and it does > fix the multivolume support (because the sectors in the radix tree could be > interpreted as being from the wrong volume). > >> I agree with you that continuing to touch ext2 is not a good idea, but I'm not >> yet convinced that now is the time to go do dax-2.0 when we haven't finished >> shipping dax-1.0. > > dax-1.0 died long ago ... I think we're up to at least DAX version 4 by now. My point is that I want to address the current slate of problems before solving new questions like "how do we support non-block based filesystems?". We just happened to land DAX in the middle of the in-progress buffer_head removal effort, so DAX should not stand in the way of where filesystems were already going. I'm arguing to complete all the false starts and half measures that are presently in DAX and then look to incrementally evolve the interfaces to something new without regressing any of it.