From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] dynamic loading, was "Ugly Q, I admit"
Date: Thu, 28 Nov 2002 01:54:12 -0500 [thread overview]
Message-ID: <008301c296ab$0d118060$ca01a8c0@cc77109e> (raw)
In-Reply-To: <20021128083812.Q6790@cackle.proxima.alt.za>
> And, last important question, how well does the chip deal with
> virtualisation?
In the "I'm a CPU" sense it is not too unlike any other mips.
Not different enough from the 4700 or the 7000 to get me upset.
brucee
next prev parent reply other threads:[~2002-11-28 6:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 21:00 [9fans] Ugly Q, I admit Russ Cox
2002-11-27 6:14 ` Bruce Ellis
2002-11-27 13:31 ` Lucio De Re
2002-11-27 18:41 ` [9fans] dynamic loading, was "Ugly Q, I admit" Bruce Ellis
2002-11-28 5:12 ` Lucio De Re
2002-11-28 5:58 ` Bruce Ellis
2002-11-28 6:38 ` Lucio De Re
2002-11-28 6:54 ` Bruce Ellis [this message]
2002-11-28 7:05 ` Lucio De Re
2002-11-27 22:49 Joel Salomon
2002-11-28 6:20 okamoto
2002-11-28 6:32 okamoto
2002-11-28 6:42 okamoto
2002-11-28 6:48 ` Ronald G. Minnich
2002-11-28 7:05 ` andrey mirtchovski
2002-11-28 9:49 okamoto
2002-11-28 16:53 ` Ronald G. Minnich
2002-12-02 4:52 ` Jack Johnson
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='008301c296ab$0d118060$ca01a8c0@cc77109e' \
--to=brucee@chunder.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).