From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Chinner Subject: Re: what's in nvdimm.git for v4.4? Date: Wed, 21 Oct 2015 13:38:47 +1100 Message-ID: <20151021023847.GB19199@dastard> References: <1445383903.6611.39.camel@intel.com> <20151021000103.GA19199@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Dan Williams Cc: "axboe@fb.com" , "akpm@linux-foundation.org" , "Wysocki, Rafael J" , "linux-kernel@vger.kernel.org" , "hch@lst.de" , "martin.petersen@oracle.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "jack@suse.cz" List-Id: linux-acpi@vger.kernel.org On Tue, Oct 20, 2015 at 05:31:18PM -0700, Dan Williams wrote: > On Tue, Oct 20, 2015 at 5:01 PM, Dave Chinner wrote: > > On Tue, Oct 20, 2015 at 11:31:45PM +0000, Williams, Dan J wrote: > >> Here is a status summary of the topic-branches nvdimm.git is tracking > >> for v4.4. Unless indicated these branches are not present in -next. > >> Please ACK, NAK, or ask for a re-post of any of the below to disposition > >> it for the merge window. > >> > >> === > >> for-4.4/dax-fixes: > >> === > > ... > >> Dave Chinner (5): > >> xfs: fix inode size update overflow in xfs_map_direct() > >> xfs: introduce BMAPI_ZERO for allocating zeroed extents > >> xfs: Don't use unwritten extents for DAX > >> xfs: DAX does not use IO completion callbacks > >> xfs: add ->pfn_mkwrite support for DAX > > > > Please drop these. They have not been reviewed yet, and because > > the changes affect more than just DAX (core XFS allocator > > functionality was changed) these need to go through the XFS tree. > > > > Ok, thanks for the heads up. For the get_user_pages() patches that > build on these fixes I'm assuming your review bandwidth is in short > supply to also give an XFS sign-off on those changes for 4.4? I'm not aware of any other patches that touch XFS. AFAIA, you haven't cc'd anything to xfs@oss.sgi.com, so it's not on my radar... > I'm wondering if we can take a conservative step forward with those > patches for 4.4. if XFS and EXT4 interactions need more time to get > worked out, which I believe they do, I can conceive just turning on > get_user_pages() support for DAX-mappings of the raw block device. Regardless of the ext4/XFS status, isn't it a bit late to be proposing brand new stuff that nobody has had time to think about for the next merge window? Cheers, Dave. -- Dave Chinner david@fromorbit.com From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753250AbbJUCjG (ORCPT ); Tue, 20 Oct 2015 22:39:06 -0400 Received: from ipmail07.adl2.internode.on.net ([150.101.137.131]:26456 "EHLO ipmail07.adl2.internode.on.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751865AbbJUCjD (ORCPT ); Tue, 20 Oct 2015 22:39:03 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DkBgAl+iZW/2ieLHldgzaBQ4JcpmMGiySLJYYYAgIBAQKBQE0BAQEBAQGBC4QtAQEBAwEnExwjBQsIAxgJJQ8FJQMhE4goB69YlCIBAQgCASAZhheFRYUNB4MagRQBBJYkjReBYIQ/iyCCH4Rcg29jhBcqNIVnAQEB Date: Wed, 21 Oct 2015 13:38:47 +1100 From: Dave Chinner To: Dan Williams Cc: "axboe@fb.com" , "akpm@linux-foundation.org" , "Wysocki, Rafael J" , "linux-kernel@vger.kernel.org" , "hch@lst.de" , "martin.petersen@oracle.com" , "linux-nvdimm@lists.01.org" , "linux-fsdevel@vger.kernel.org" , "linux-acpi@vger.kernel.org" , "jack@suse.cz" Subject: Re: what's in nvdimm.git for v4.4? Message-ID: <20151021023847.GB19199@dastard> References: <1445383903.6611.39.camel@intel.com> <20151021000103.GA19199@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 20, 2015 at 05:31:18PM -0700, Dan Williams wrote: > On Tue, Oct 20, 2015 at 5:01 PM, Dave Chinner wrote: > > On Tue, Oct 20, 2015 at 11:31:45PM +0000, Williams, Dan J wrote: > >> Here is a status summary of the topic-branches nvdimm.git is tracking > >> for v4.4. Unless indicated these branches are not present in -next. > >> Please ACK, NAK, or ask for a re-post of any of the below to disposition > >> it for the merge window. > >> > >> === > >> for-4.4/dax-fixes: > >> === > > ... > >> Dave Chinner (5): > >> xfs: fix inode size update overflow in xfs_map_direct() > >> xfs: introduce BMAPI_ZERO for allocating zeroed extents > >> xfs: Don't use unwritten extents for DAX > >> xfs: DAX does not use IO completion callbacks > >> xfs: add ->pfn_mkwrite support for DAX > > > > Please drop these. They have not been reviewed yet, and because > > the changes affect more than just DAX (core XFS allocator > > functionality was changed) these need to go through the XFS tree. > > > > Ok, thanks for the heads up. For the get_user_pages() patches that > build on these fixes I'm assuming your review bandwidth is in short > supply to also give an XFS sign-off on those changes for 4.4? I'm not aware of any other patches that touch XFS. AFAIA, you haven't cc'd anything to xfs@oss.sgi.com, so it's not on my radar... > I'm wondering if we can take a conservative step forward with those > patches for 4.4. if XFS and EXT4 interactions need more time to get > worked out, which I believe they do, I can conceive just turning on > get_user_pages() support for DAX-mappings of the raw block device. Regardless of the ext4/XFS status, isn't it a bit late to be proposing brand new stuff that nobody has had time to think about for the next merge window? Cheers, Dave. -- Dave Chinner david@fromorbit.com