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] Plan9 on the Cell...
Date: Fri, 10 Jun 2005 21:45:06 -0600	[thread overview]
Message-ID: <Pine.LNX.4.58.0506102141380.24498@enigma.lanl.gov> (raw)
In-Reply-To: <Pine.BSI.4.61.0506101737000.11929@malasada.lava.net>



On Fri, 10 Jun 2005, Tim Newsham wrote:

> What about standard VM perks like being able to share device drivers
> from a popular operating system?  Does Vanderbilt support that?

my reading (incomplete) of VT is that you get, among other things, an 
emulated NE 2000 (That's my reading!). 

So, I don't know what to say ...

You really do want virtual devices like the xen front end/back end 
drivers, since you can do better with a shared queue than with emulating 
some wacky legacy device (I think).

So, plan 9 will run unmodified under VT, but we do want to continue to 
have a plan 9 that is built for xen, long term.

Tim, I'll contact you w.r.t. Xen 3.0 and we can figure out what to do. 
I've started but 3.0 is still moving target mode -- first thing is to get 
it on my desktop and hope it will work. You can't have 2.0 and 3.0 on the 
same machine, so I am not willing to muck up my laptop just yet with 3.0 
given how well 2.0 is working for me. I did a demo today with a "cluster" 
on my laptop -- the compute nodes boot in 1 second on Xen.

ron


  reply	other threads:[~2005-06-11  3:45 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 19:05 Paul Lalonde
2005-05-24 19:26 ` Eric Van Hensbergen
2005-05-24 23:04   ` Paul Lalonde
2005-05-24 23:18     ` Jack Johnson
2005-05-24 23:27       ` Eric Van Hensbergen
2005-05-24 23:30       ` Paul Lalonde
2005-05-25  3:11         ` Bruce Ellis
2005-05-27 16:53         ` Paul Lalonde
2005-05-28  6:29           ` andrey mirtchovski
2005-05-28 14:51             ` Eric Van Hensbergen
2005-05-28 17:45             ` Ronald G. Minnich
2005-05-28 17:56               ` Ronald G. Minnich
2005-05-28 18:11                 ` Jack Johnson
2005-05-28 18:31                   ` jmk
2005-05-28 18:34                 ` Paul Lalonde
2005-05-29  6:35                 ` Noah Evans
2005-05-29  9:26                   ` Charles Forsyth
2005-05-30 20:43                     ` Eric Van Hensbergen
2005-06-03 11:55                   ` Noah Evans
2005-06-03 12:57                     ` Eric Van Hensbergen
2005-06-03 15:46                     ` Dave Eckhardt
2005-06-03 16:43                       ` Ronald G. Minnich
2005-06-03 17:33                         ` Brantley Coile
2005-06-03 21:22                         ` David Leimbach
2005-05-29  9:26                 ` Charles Forsyth
2005-05-24 23:26     ` Eric Van Hensbergen
2005-05-25  9:10       ` C H Forsyth
2005-05-25 15:07         ` Ronald G. Minnich
     [not found]           ` <a4e6962a050525081244ed619d@mail.gmail.com>
2005-05-25 15:13             ` Fwd: " Eric Van Hensbergen
2005-05-25 15:30           ` C H Forsyth
2005-06-21 16:46   ` Eric Van Hensbergen
2005-06-10 14:04 ` Eric Van Hensbergen
2005-06-10 16:44   ` Paul Lalonde
2005-06-10 18:43     ` Bruce Ellis
2005-06-11  3:17     ` Ronald G. Minnich
2005-06-11  3:38       ` Tim Newsham
2005-06-11  3:45         ` Ronald G. Minnich [this message]
2005-06-11 19:36           ` C H Forsyth
2005-06-12 21:36       ` arisawa
2005-06-12 22:55         ` Eric Van Hensbergen
2005-06-12 23:54           ` George Gensure
2005-06-13  2:39         ` Ronald G. Minnich
2005-06-13  5:17           ` Martin C. Atkins
2005-05-28 19:21 jmk

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.0506102141380.24498@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).