Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753724AbbFVQce (ORCPT ); Mon, 22 Jun 2015 12:32:34 -0400 Received: from verein.lst.de ([213.95.11.211]:42967 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751807AbbFVQc1 (ORCPT ); Mon, 22 Jun 2015 12:32:27 -0400 Date: Mon, 22 Jun 2015 18:32:24 +0200 From: Christoph Hellwig To: Jeff Moyer Cc: Christoph Hellwig , Dan Williams , Jens Axboe , "linux-nvdimm@lists.01.org" , "linux-kernel@vger.kernel.org" , Linux ACPI , linux-fsdevel , Ingo Molnar Subject: Re: [PATCH 14/15] libnvdimm: support read-only btt backing devices Message-ID: <20150622163224.GA9168@lst.de> References: <20150621135406.GA9572@lst.de> <20150622063028.GA30434@lst.de> <20150622072844.GA31263@lst.de> <20150622154138.GC7952@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 612 Lines: 12 On Mon, Jun 22, 2015 at 12:00:54PM -0400, Jeff Moyer wrote: > Right now, the guidance should be to always use btt since there are no > applications that are directly taking advantage of persistent memory > (that I know). I expect documentation would take care of that. I also > expect that, as applications add support, they would note the > requirement for dax mountpoints in their documentation. It's not just DAX. Avoiding the overhead for anything else is another good reason. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/