From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Disk naming (Was Re: [PATCH] Guest boot loadersupport [1/2]) Date: Fri, 15 Apr 2005 12:57:26 -0500 Message-ID: <42600086.6020306@us.ibm.com> References: <200504150043.32317.mark.williamson@cl.cam.ac.uk> <200504151743.52373.mark.williamson@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Adam Heath Cc: "xen-devel@lists.xensource.com" , Mark Williamson List-Id: xen-devel@lists.xenproject.org Adam Heath wrote: >It does. So, it's the blkback in dom0 that requires a device node. How about >it the blkback were extended to support files in filesystems? > > I think the hardest thing to deal with is the fact that the control messages are limited to 60 bytes meaning that if you changed the be_vbd_create message to pass file names instead of device types you'd have to support continuations to suport filenames that are > ~40 bytes long. The registry will make this a lot easier since the blkif_be device could just read a filename out of the registry. I've thought about changing the blkif_be driver to be able to access the file ops directly before and this has been the limiting factor in my mind (unless someone else has a more creative solution :-)). Regards, Anthony Liguori >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >