From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices Date: Tue, 23 Jun 2015 12:10:04 +0200 Message-ID: <20150623101004.GE24894@lst.de> 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=us-ascii Cc: Christoph Hellwig , 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: Jeff Moyer Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jun 22, 2015 at 02:32:53PM -0400, Jeff Moyer wrote: > How will this subdivision be recorded? Not all NVDIMMs support the > label specification. Labeks woud be preferable, it's a pity the spec is so vague. > Sysadmins are already familiar with partitions; I'm not sure why we'd > deviate from that here. What am I missing? The layering architecture I guess?