Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753464AbbEOE1K (ORCPT ); Fri, 15 May 2015 00:27:10 -0400 Received: from g9t5009.houston.hp.com ([15.240.92.67]:35145 "EHLO g9t5009.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753161AbbEOE1H convert rfc822-to-8bit (ORCPT ); Fri, 15 May 2015 00:27:07 -0400 From: "Elliott, Robert (Server Storage)" To: Dan Williams , "Kani, Toshimitsu" CC: Neil Brown , Greg KH , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" Subject: RE: [Linux-nvdimm] [PATCH v2 18/20] libnd: infrastructure for btt devices Thread-Topic: [Linux-nvdimm] [PATCH v2 18/20] libnd: infrastructure for btt devices Thread-Index: AQHQjNQeVf5lYy5WKEaMFENGhYKYB518Nj0AgAA9TFA= Date: Fri, 15 May 2015 04:25:24 +0000 Message-ID: <94D0CD8314A33A4D9D801C0FE68B40295A9068BF@G9W0745.americas.hpqcorp.net> References: <20150428181203.35812.60474.stgit@dwillia2-desk3.amr.corp.intel.com> <20150428182551.35812.97856.stgit@dwillia2-desk3.amr.corp.intel.com> <1431448400.24419.99.camel@misato.fc.hp.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [16.210.192.240] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1285 Lines: 36 > -----Original Message----- > From: Linux-nvdimm [mailto:linux-nvdimm-bounces@lists.01.org] On Behalf > Of Dan Williams > Sent: Thursday, May 14, 2015 7:42 PM > To: Kani, Toshimitsu > Cc: Neil Brown; Greg KH; linux-kernel@vger.kernel.org; linux- > nvdimm@lists.01.org > Subject: Re: [Linux-nvdimm] [PATCH v2 18/20] libnd: infrastructure for > btt devices > ... > So we can fix this to be at least as stable as the backing device > names [1], but as far as I can see we would need to start using the > backing device name in the btt device name. A strawman proposal is to > append 's' to indicated 'sectored'. So /dev/pmem0s is the btt > instance fronting /dev/pmem0. Other examples: > > /dev/pmem0p1s > /dev/ndblk0.0s > /dev/ndblk0.0p1s > ... > > Thoughts? > > [1]: https://lists.01.org/pipermail/linux-nvdimm/2015-April/000636.html I like that; it also hints to the user that another driver has already claimed /dev/pmem0, similar to how the presence of /dev/sda1, /dev/sda2, etc. hints that a program has partitioned /dev/sda. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/