From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Wilcox Subject: Re: Persistent memory interface Date: Fri, 19 Jun 2015 12:48:25 -0400 Message-ID: <20150619164825.GB1971@linux.intel.com> References: Reply-To: device-mapper development Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dm-devel-bounces@redhat.com Errors-To: dm-devel-bounces@redhat.com To: Mikulas Patocka Cc: Boaz Harrosh , Thomas Gleixner , Andrew Morton , linux-nvdimm@ml01.01.org, Keith Busch , Andy Lutomirski , Jens Axboe , dm-devel@redhat.com, Borislav Petkov , "H. Peter Anvin" , Ross Zwisler , Christoph Hellwig List-Id: dm-devel.ids On Fri, Jun 19, 2015 at 12:33:09PM -0400, Mikulas Patocka wrote: > If I want to use persistent memory in another driver, for a different > purpose, how can I make sure that that drivers/block/pmem.c doesn't attach > to this piece of memory and export it? It seems not possible. > drivers/block/pmem.c attaches to everything without regard that there may > be other users of persistent memory. You need to look at the patches that Dan has been posting to add support for Labels (and NFIT and ...). Those weren't available earlier because the label spec wasn't public. > BTW. some journaling filesystems assume that 512-byte sector is written > atomically. drivers/block/pmem.c breaks this requirement. Persistent > memory only gurantees 8-byte atomic writes. ... and that's addressed by the BTT patches.