From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Moyer Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices Date: Mon, 22 Jun 2015 14:32:53 -0400 Message-ID: References: <20150617235209.12943.24419.stgit@dwillia2-desk3.amr.corp.intel.com> <20150617235458.12943.23425.stgit@dwillia2-desk3.amr.corp.intel.com> <20150622163453.GA9187@lst.de> <20150622164837.GB9393@lst.de> Mime-Version: 1.0 Content-Type: text/plain Cc: Dan Williams , Jens Axboe , "linux-nvdimm\@lists.01.org" , Neil Brown , Greg KH , "linux-kernel\@vger.kernel.org" , Ingo Molnar , Linux ACPI , linux-fsdevel To: Christoph Hellwig Return-path: In-Reply-To: <20150622164837.GB9393@lst.de> (Christoph Hellwig's message of "Mon, 22 Jun 2015 18:48:37 +0200") Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Christoph Hellwig writes: > On Mon, Jun 22, 2015 at 09:48:03AM -0700, Dan Williams wrote: >> Only if you abandon BTT on partitions, which at this point it seems >> you're boldly committed to doing. It's unacceptable to drop BTT on >> the floor so I'll take a look at making BTT per-disk only for 4.2. > > If by partitions you mean block layer partitions: yes. If by partitions > you mean subdivision of nvdimms: no. How will this subdivision be recorded? Not all NVDIMMs support the label specification. Sysadmins are already familiar with partitions; I'm not sure why we'd deviate from that here. What am I missing? -Jeff -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in