9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 8c question
Date: Sun, 10 Jul 2005 18:57:55 -0600	[thread overview]
Message-ID: <Pine.LNX.4.58.0507101853241.12286@enigma.lanl.gov> (raw)
In-Reply-To: <eaf7ffeb94093a1af9c5b04c2c0aa4f9@terzarima.net>



On Sat, 9 Jul 2005, Charles Forsyth wrote:

> not if i start to wonder about the surrounding software, when such
> sloppy assumptions are made in something as important as the interface.  
> i'd already thought, glancing at it months ago, that there seemed to be
> rather a lot of interface, which also made me wonder, but i'd made a
> mental note to revisit it when i had more time.

we have been trying and failing to get the xen guys interested in 9p as 
the backbone comms for inter-domain communication in Xen, both dom0->domU 
and domU->domU. 

What we're lacking is anyone with a time to write the proof-of-concept 
implementation. I wish we could get it done, because the inter-domain 
comms in xen just keep getting more and more complex. 

It's been hard to even argue that you could use the same
open/read/write/close interface for a disk and an ethernet device. "Linux
doesn't do that ...". So we have a disk virtual device and an ethernet
virtual device that are very, very different in implementation, even
though it's basically a 2-way shared-memory fifo queue in each case. I
really think they could be the same.

ron


  reply	other threads:[~2005-07-11  0:57 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 23:17 Tim Newsham
2005-07-02 12:43 ` Charles Forsyth
2005-07-05  2:36   ` David Leimbach
2005-07-05 14:47     ` Ronald G. Minnich
2005-07-05 15:27     ` Latchesar Ionkov
2005-07-05 15:33       ` Ronald G. Minnich
2005-07-05 18:33         ` Tim Newsham
2005-07-05 15:35       ` David Leimbach
2005-07-07 23:08         ` Charles Forsyth
2005-07-08  0:06           ` Ronald G. Minnich
2005-07-08  0:27             ` Russ Cox
2005-07-08 14:36               ` Ronald G. Minnich
2005-07-08 19:03                 ` jmk
2005-07-08 19:40                   ` Charles Forsyth
2005-07-09  1:02                   ` Ronald G. Minnich
2005-07-08  3:31           ` Tim Newsham
2005-07-08 11:14             ` Charles Forsyth
2005-07-09  1:04             ` Tim Newsham
2005-07-09  9:40               ` Charles Forsyth
2005-07-11  0:57                 ` Ronald G. Minnich [this message]
2005-07-11  1:26                   ` [9fans] Xen comms Tim Newsham
2005-07-11 19:21                     ` Eric Van Hensbergen
2005-07-11 19:23                   ` [9fans] 8c question Eric Van Hensbergen
2005-07-11 19:58                     ` Ronald G. Minnich
2005-07-11 20:05                       ` Eric Van Hensbergen
2005-07-11 20:15                         ` Ronald G. Minnich
2005-07-11 20:35                           ` Eric Van Hensbergen
2005-07-11 20:38                             ` Ronald G. Minnich
2005-07-11 21:03                               ` Eric Van Hensbergen
2005-07-11 21:09                                 ` Ronald G. Minnich
2005-07-11 21:13                                   ` Eric Van Hensbergen

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=Pine.LNX.4.58.0507101853241.12286@enigma.lanl.gov \
    --to=rminnich@lanl.gov \
    --cc=9fans@cse.psu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).