From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] why I'm messing with python: mercurial
Date: Sun, 24 Dec 2006 09:30:53 +0000 [thread overview]
Message-ID: <69898e3538bf13a71cf2403dd5e3d48e@hamnavoe.com> (raw)
In-Reply-To: <13426df10612232126p669bd6eaq1411e0546c5dcd7@mail.gmail.com>
> I can't wait to try out plan 9 + xen on a
> dual-core, it's already reasonably fast.
I've run it on a two-processor VIA vt310. An extra cpu does help with
responsiveness. Would it be worthwhile to support multiple virtual
processors in the guest Plan 9? It's just a matter of coding the
start-up for the extra processors ("just" - of course it's
undocumented).
-- Richard
next prev parent reply other threads:[~2006-12-24 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 5:26 ron minnich
2006-12-24 9:30 ` Richard Miller [this message]
2006-12-25 1:00 ` Jack Johnson
2006-12-24 10:25 ` Harri Haataja
2006-12-24 17:15 ` David Leimbach
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=69898e3538bf13a71cf2403dd5e3d48e@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).