From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by ml01.01.org (Postfix) with ESMTP id AEF131A1E15 for ; Mon, 15 Aug 2016 14:11:07 -0700 (PDT) Date: Mon, 15 Aug 2016 15:11:06 -0600 From: Ross Zwisler Subject: Re: [PATCH 0/7] re-enable DAX PMD support Message-ID: <20160815211106.GA31566@linux.intel.com> References: <20160815190918.20672-1-ross.zwisler@linux.intel.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Dan Williams Cc: Theodore Ts'o , "linux-nvdimm@lists.01.org" , Dave Chinner , "linux-kernel@vger.kernel.org" , Linux MM , Andreas Dilger , Alexander Viro , Jan Kara , linux-fsdevel , linux-ext4 , Andrew Morton List-ID: On Mon, Aug 15, 2016 at 01:21:47PM -0700, Dan Williams wrote: > On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler > wrote: > > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > > locking. This series allows DAX PMDs to participate in the DAX radix tree > > based locking scheme so that they can be re-enabled. > > Looks good to me. > > > This series restores DAX PMD functionality back to what it was before it > > was disabled. There is still a known issue between DAX PMDs and hole > > punch, which I am currently working on and which I plan to address with a > > separate series. > > Perhaps we should hold off on applying patch 6 and 7 until after the > hole-punch fix is ready? Sure, I'm cool with holding off on patch 7 (the Kconfig change) until after the hole punch fix is ready. I don't see a reason to hold off on patch 6, though? It stands on it's own, implements the correct locking, and doesn't break anything. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm