Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751858AbbFVTDI (ORCPT ); Mon, 22 Jun 2015 15:03:08 -0400 Received: from mail-wg0-f52.google.com ([74.125.82.52]:35689 "EHLO mail-wg0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751010AbbFVTC4 (ORCPT ); Mon, 22 Jun 2015 15:02:56 -0400 MIME-Version: 1.0 In-Reply-To: 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> Date: Mon, 22 Jun 2015 12:02:54 -0700 Message-ID: Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices From: Dan Williams To: Jeff Moyer 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 Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1266 Lines: 30 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-kernel" in Please read the FAQ at http://www.tux.org/lkml/