From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Butterworth Subject: Re: Re: Interdomain comms Date: Sat, 07 May 2005 00:13:05 +0100 Message-ID: <1115421185.4141.18.camel@localhost> References: <0BAE938A1E68534E928747B9B46A759A6CF3AC@EXCNYSM0A1AH.nysemail.nyenet> <1115325448.12082.79.camel@localhost> <427B20B9.1010101@hp.com> <1115381693.18929.159.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain 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: "Ronald G. Minnich" Cc: Mike Wray , xen-devel@lists.xensource.com, Eric Van Hensbergen List-Id: xen-devel@lists.xenproject.org I skimmed what I could find immediately on 9P: http://www.cs.bell-labs.com/sys/man/5/INDEX.html and came to the conclusion that what I proposed is lower level and more general (it's also simpler but, given that it's not doing the same thing, that isn't really significant). You could implement 9P on top of my IDC API proposal---and this might very well be a valid thing to do given that some sort of higher level protocol is required---but, with what I proposed, you could also do things like implement a stack of software I/O virtualization functions and send the bulk data between the top of the stack and the bottom without going via all the components in the middle. My 10 mins of 9P experience indicates that 9P doesn't have anything like that. Or does it---any pointers to good 9P documentation? Harry