[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] RFC: "local" communications


  • To: "Nivedita Singhvi" <niv@xxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Wed, 15 Jun 2005 23:32:30 +0100
  • Cc: Lon Hohberger <lhh@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 15 Jun 2005 22:31:35 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcVx9yUj6tzJ5ItFRseM3zdMsSDvTgAAf93A
  • Thread-topic: [Xen-devel] RFC: "local" communications

 

> -----Original Message-----
> From: Nivedita Singhvi [mailto:niv@xxxxxxxxxx] 
> Sent: 15 June 2005 23:11
> To: Ian Pratt
> Cc: Rik van Riel; xen-devel@xxxxxxxxxxxxxxxxxxx; Lon Hohberger
> Subject: Re: [Xen-devel] RFC: "local" communications
> 
> Ian Pratt wrote:
> 
> > For relatively static stuff (e.g. textual configuration data), it 
> > would be reasonable to use xenbus/xenstore. We could give 
> each domain 
> > a subtree in the store that it can read/write via a 
> /proc/sys interface.
> 
> Ian, how flexible is the format/layout of the xenstore going 
> to be? Does it allow for more of a general purpose use? That 
> would be neat..

It enables something akin to /proc. i.e. you can have an arbitrary
hierarchy of files. To retain the same spirit as everything else in
xenstore it would be preferable that both file names and contents were
text (rather than binary).

I think I quite like the idea of having a /proc/sys interface onto
xenstore. We'll still need the console multiplexing approach for
stream/datagram data.

Ian



  

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.