From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 2B21B81EE3 for ; Mon, 23 Jan 2017 08:01:05 -0800 (PST) Date: Mon, 23 Jan 2017 17:01:03 +0100 From: Christoph Hellwig Subject: Re: [PATCH 00/13] dax, pmem: move cpu cache maintenance to libnvdimm Message-ID: <20170123160103.GC517@lst.de> References: <148488421301.37913.12835362165895864897.stgit@dwillia2-desk3.amr.corp.intel.com> <20170121175212.GA28180@lst.de> 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: "x86@kernel.org" , Tony Luck , Jan Kara , Mike Snitzer , "linux-nvdimm@lists.01.org" , Jens Axboe , Matthew Wilcox , "linux-kernel@vger.kernel.org" , Ingo Molnar , Al Viro , "H. Peter Anvin" , "linux-fsdevel@vger.kernel.org" , Thomas Gleixner , "dm-devel@redhat.com" , Linus Torvalds , Christoph Hellwig List-ID: On Sun, Jan 22, 2017 at 09:30:23AM -0800, Dan Williams wrote: > So are you saying we need a way to go from a block_device inode to a > dax_device inode and then look up the dax_operations from there? > > A filesystem, if it so chooses, could mount on top of the dax_device > inode directly? Sentence 1: maybe if we have to. Sentence 2: absolutely. > I did add a dax_superblock for the device-dax character device > representation I could refactor that so the block_device presentation > of a namespace and a character device presentation are just different > layers on top of the base-level dax inode. That's a good start. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm