Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752546AbbEJJq3 (ORCPT ); Sun, 10 May 2015 05:46:29 -0400 Received: from mail-wi0-f170.google.com ([209.85.212.170]:37814 "EHLO mail-wi0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752178AbbEJJqZ (ORCPT ); Sun, 10 May 2015 05:46:25 -0400 Date: Sun, 10 May 2015 11:46:19 +0200 From: Ingo Molnar To: Dan Williams Cc: Rik van Riel , Linus Torvalds , John Stoffel , Dave Hansen , Linux Kernel Mailing List , Boaz Harrosh , Jan Kara , Mike Snitzer , Neil Brown , Benjamin Herrenschmidt , Heiko Carstens , Chris Mason , Paul Mackerras , "H. Peter Anvin" , Christoph Hellwig , Alasdair Kergon , "linux-nvdimm@lists.01.org" , Mel Gorman , Matthew Wilcox , Ross Zwisler , Martin Schwidefsky , Jens Axboe , "Theodore Ts'o" , "Martin K. Petersen" , Julia Lawall , Tejun Heo , linux-fsdevel , Andrew Morton Subject: Re: "Directly mapped persistent memory page cache" Message-ID: <20150510094619.GA15198@gmail.com> References: <554BA748.9030804@linux.intel.com> <20150507191107.GB22952@gmail.com> <554CBE17.4070904@redhat.com> <20150508140556.GA2185@gmail.com> <21836.51957.715473.780762@quad.stoffel.home> <554CEB5D.90209@redhat.com> <20150509084510.GA10587@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1589 Lines: 41 * Dan Williams wrote: > > "Directly mapped pmem integrated into the page cache": > > ------------------------------------------------------ > Nice, I think it makes sense as an area that gets reserved at file > system creation time. You are not proposing that this gets > automatically reserved at the device level, right? [...] Well, it's most practical if the device does it automatically (the layout is determined prior filesystem creation), and the filesystem does not necessarily have to be aware of it - but obviously as a user opt-in. > [...] For the use cases of persistent memory in the absence of a > file system (in-kernel managed hierarchical storage driver, or > mmap() the pmem block device directly) there's still a need for > pfn-based DAX. [...] Yes, but knowing that there's a sane model we can take a hard stance against pfn proliferation and say: 'we let pfns this far and no farther'. > [...] In other words, simple usages skip the overhead. They assume > pfns only, discover those pmem pfns via ->direct_access(), and > arrange for exclusive block device ownership. Everything else that > requires struct page in turn requires a file system to have opt-ed > into this reservation and provide pmem-struct-page infrastructure, > pmem-aware-DIO etc. Yes. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/