From: Joe Batt <Joe@soliddesign.net>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: request : qemu-smp as target
Date: Tue, 17 May 2005 15:41:34 -0500 [thread overview]
Message-ID: <1116362494.20056.50.camel@fred.ofc.soliddesign.net> (raw)
In-Reply-To: <200505172121.28546.paul@codesourcery.com>
On Tue, 2005-05-17 at 21:21 +0100, Paul Brook wrote:
> > What inter processor synchronization issues are there? Could you take
> > this a step further and use processes on different machines for each
> > processor? (There are many shared memory implementations to choose
> > from.) Are there so many resources shared
> > between the CPUs to make this a ridiculous proposition?
>
> Baically most SMP/shared memory systems assume very low latency communication
> between CPUs and memory. For example on opteron systems remote memory latency
> is of the order of 200 cpu cycles. Typical ethernet latency is several
> million cycles.
But how often will the virtual CPUs need the same page and is there any
other shared resource other than memory? I don't know how independent
each CPU is. Though in side discussions, everyone agrees with you, I
haven't seen numbers to convince my gut. If page only needs to be
faulted back and forth every couple million cycles, then it might work.
> The only solution I can imagine being even vaguely worthwhile is a running
> user-mode qemu on top of a native openmozix system.
OpenMosix is very interesting, but is a pain to setup. How about this:
ssh -f host1 qemu -cpu-server $KEY
ssh -f host2 qemu -cpu-server $KEY
qemu -cpu-client host1:$KEY \
-cpu-client host2:$KEY \
-hda server.image
> > I have ignorantly implemented an SH2 emulator,
>
> Cool. Any chance you're going to make these changes publicly available?
It was a Java implementation for a customer. Not my property and not
integrated with any free software.
> Paul
--
Joe Batt <Joe@soliddesign.net>
next prev parent reply other threads:[~2005-05-17 22:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 9:37 [Qemu-devel] Re: request : qemu-smp as target Blue Swirl
2005-05-14 11:31 ` Paul Brook
2005-05-14 15:22 ` Blue Swirl
2005-05-14 12:16 ` Fabrice Bellard
2005-05-14 13:11 ` Jonas Maebe
2005-05-14 14:46 ` Blue Swirl
2005-05-14 16:55 ` Joe Batt
2005-05-17 20:21 ` Paul Brook
2005-05-17 20:41 ` Joe Batt [this message]
2005-05-17 20:59 ` Paul Brook
2005-05-18 11:29 ` Mark Williamson
2005-05-18 21:19 ` Re[2]: " Igor Shmukler
2005-05-18 11:25 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 13:17 octane indice
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=1116362494.20056.50.camel@fred.ofc.soliddesign.net \
--to=joe@soliddesign.net \
--cc=paul@codesourcery.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).