From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [PATCH 5/6] libxl: introduce libxl__alloc_vdev Date: Tue, 3 Apr 2012 14:17:52 +0100 Message-ID: <20346.63616.101912.260089@mariner.uk.xensource.com> References: <1332856772-30292-5-git-send-email-stefano.stabellini@eu.citrix.com> <20337.63133.683848.208682@mariner.uk.xensource.com> <20341.49280.31751.307404@mariner.uk.xensource.com> <20345.53429.51575.373166@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 5/6] libxl: introduce libxl__alloc_vdev"): > I don't feel that strongly about this, but given that the naming scheme > used in the guest is actually arbitrary at the moment (as in not document > or well defined anywhere), I would start the dynamic space before the > 26th device: I have the feeling that after "xvdz" the behavior is going > to be even less "defined". I suggest "xvdm" as a starting point. That's fine, if the starting point is configurable. > > However, that does not mean that the guest should not document its > > naming conventions. Perhaps this needs to be clarified in the > > document. > > Right, but unless I am missing something there isn't such a thing at the > moment, at least in Linux. > > I'll try to come up with a linux devid to vdev function true to the > original. That would be good. If you felt like documenting the Linux behaviour properly that would be good. The section "Notes on Linux as a guest" in docs/misc/vbd-interface.text. TBH I think Linux /should/ use the same numbering scheme as the name supplied in the host config file, just for sanity's sake. Ian.