From: Joseph Stewart <joseph.stewart@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] SMP
Date: Wed, 28 Jul 2004 16:35:34 -0400 [thread overview]
Message-ID: <2781f0204072813352ce36ad1@mail.gmail.com> (raw)
In-Reply-To: <1091045449.22121.37.camel@localhost>
I say this half-joking and half-serious, but how about a qemu
emulation for the Transputer core?...
(http://www.embedded.com.au/reference/transputers.html and
http://www.classiccmp.org/transputer/).
Seriously, I don't know enough about the internal structure of QEMU to
know if this is even a reasonable or desirable feature. And then
there's the issue of learning OCCAM.
-joe
On Wed, 28 Jul 2004 15:10:50 -0500, Joe Batt <joe@soliddesign.net> wrote:
> I realize that this may be pushing the future a bit, I just wanted to
> start the discussion.
>
> What challenges do we (or does Fabrice) face
> - creating an qemu SMP guest?
> - multithreading qemu to utilize a SMP host?
> - integrating with something like mosix so you could build a virtual 50
> CPU box in a lab across 50 real machines (or a 250 CPU box on 50
> machines to avoid waiting on IO)
> - how would numa figure into this (I'm completely ignorant of what a
> numa machine looks like)
>
> I am very interested in single image clusters (as a spectator), but what
> I've seen so far is coupling machines at a level that seems to high and
> complex to me. It seems silly that each machine has to have a full OS
> installed and configured just right. Building a big single image
> machine on linked VMs would allow us to run qemu on a stripped down OS
> (just drivers and basic services) or a heterogeneous network (even a mix
> of linux kernels would beat mosix).
>
> Thanks for any consideration.
> Joe
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2004-07-28 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 16:42 [Qemu-devel] Win32 usermode only network possible? [was: multiple VMs] Mike Nordell
2004-04-07 20:10 ` Fabrice Bellard
2004-04-07 22:04 ` John R. Hogerhuis
2004-04-07 22:16 ` Joe Batt
2004-04-07 23:04 ` John R. Hogerhuis
2004-04-08 1:46 ` [Qemu-devel] Win32 usermode only network possible? [was:multiple VMs] kazu
2004-04-07 23:29 ` [Qemu-devel] Win32 usermode only network possible? art yerkes
2004-04-15 0:41 ` [Qemu-devel] Win32 usermode only network possible? [was: multiple VMs] Rusty Russell
2004-04-15 21:36 ` Fabrice Bellard
2004-04-20 23:00 ` [Qemu-devel] User mode only network progress Fabrice Bellard
2004-04-20 23:38 ` John R. Hogerhuis
2004-04-21 7:20 ` Jean-Michel POURE
2004-04-21 19:18 ` Fabrice Bellard
2004-04-21 19:37 ` Rudi Lippert
2004-04-21 22:08 ` Fabrice Bellard
2004-04-22 0:23 ` Fabrice Bellard
2004-04-22 6:44 ` Jean-Michel POURE
2004-04-22 21:30 ` Renzo Davoli
2004-04-23 17:34 ` Rudi Lippert
2004-07-28 20:10 ` [Qemu-devel] SMP Joe Batt
2004-07-28 20:35 ` Joseph Stewart [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-06 9:40 Jacek Poplawski
2006-04-06 17:06 ` Pascal Terjan
2006-04-10 11:36 ` Rakotomandimby Mihamina
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=2781f0204072813352ce36ad1@mail.gmail.com \
--to=joseph.stewart@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).