All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Butterworth <harry@hebutterworth.freeserve.co.uk>
To: "Ronald G. Minnich" <rminnich@lanl.gov>
Cc: Mike Wray <mike.wray@hp.com>,
	xen-devel@lists.xensource.com,
	Eric Van Hensbergen <ericvh@users.sourceforge.net>
Subject: Re: Re: Interdomain comms
Date: Sat, 07 May 2005 00:13:05 +0100	[thread overview]
Message-ID: <1115421185.4141.18.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.58.0505060940420.10357@enigma.lanl.gov>

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

  parent reply	other threads:[~2005-05-06 23:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 15:18 please help: initialize XEND for my debug-FE/BE.c Aggarwal, Vikas (OFT)
2005-05-05 20:37 ` Harry Butterworth
     [not found]   ` <427B20B9.1010101@hp.com>
2005-05-06 12:14     ` Interdomain comms Harry Butterworth
2005-05-06 13:39       ` Mark Williamson
2005-05-06 16:04       ` Ronald G. Minnich
2005-05-06 16:49         ` Eric Van Hensbergen
2005-05-06 23:13         ` Harry Butterworth [this message]
2005-05-07  0:19           ` Eric Van Hensbergen
2005-05-07 13:26             ` Harry Butterworth
2005-05-07 14:57               ` Eric Van Hensbergen
2005-05-07 16:15               ` Ronald G. Minnich
2005-05-07 17:10                 ` Keir Fraser
2005-05-07 21:22                   ` Eric Van Hensbergen
2005-05-07 17:17                 ` Harry Butterworth
2005-05-07 21:29                   ` Eric Van Hensbergen
2005-05-07 22:11                     ` Harry Butterworth
2005-05-08  0:57                       ` Eric Van Hensbergen
2005-05-08  8:19                         ` Andrew Warfield
2005-05-08 15:27                           ` Eric Van Hensbergen
2005-05-10  8:31                           ` Mike Wray
2005-05-10 10:09                             ` Andrew Warfield
2005-05-10 14:30                               ` Mike Wray
2005-05-10 14:51                               ` Harry Butterworth
     [not found]                                 ` <eacc82a405051008243195164c@mail.gmail.com>
2005-05-10 15:26                                   ` Andrew Warfield
2005-05-10 16:42                                     ` Harry Butterworth
2005-05-08  8:36                         ` Harry Butterworth
2005-05-08 16:18                           ` Eric Van Hensbergen
2005-05-08 17:48                             ` Harry Butterworth
2005-05-06 16:57       ` Nivedita Singhvi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1115421185.4141.18.camel@localhost \
    --to=harry@hebutterworth.freeserve.co.uk \
    --cc=ericvh@users.sourceforge.net \
    --cc=mike.wray@hp.com \
    --cc=rminnich@lanl.gov \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.