From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices Date: Mon, 22 Jun 2015 12:02:54 -0700 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; charset=UTF-8 Cc: Christoph Hellwig , Jens Axboe , "linux-nvdimm@lists.01.org" , Neil Brown , Greg KH , "linux-kernel@vger.kernel.org" , Ingo Molnar , Linux ACPI , linux-fsdevel To: Jeff Moyer Return-path: In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jun 22, 2015 at 11:32 AM, Jeff Moyer wrote: > 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. ...and the ones that do only use labels for resolving aliasing, not partitioning. > Sysadmins are already familiar with partitions; I'm not sure why we'd > deviate from that here. What am I missing? I don't see the need to re-invent partitioning which is the path this requested rework is putting us on... However, when the need arises for smaller granularity BTT we can have the partition fight then. To be clear, I believe that need is already here today, but I'm not in a position to push that agenda at this late date. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in