From: Jamie Lokier <jamie@shareable.org>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: Victor Vasilchenko <vvasilchenko@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU redesigned for MPI (Message Passing Interface)
Date: Mon, 16 Nov 2009 22:57:22 +0000 [thread overview]
Message-ID: <20091116225722.GF12063@shareable.org> (raw)
In-Reply-To: <f284c33d0911160101j7d71f0f8p4ac41617b0ec7bd0@mail.gmail.com>
Mulyadi Santosa wrote:
> Hi Victor...
>
> On 11/13/09, Victor Vasilchenko <vvasilchenko@gmail.com> wrote:
> > The only BIG question - what virtualization software can support MPI to
> > effectively work on cluster ?
> >
> > I am asking this question to QEMU team cause I believe QEMU can be the one.
> > If you have any ideas or experiments or information - please share with me.
> >
> > Kind Regards,
> > Victor.
> >
>
> If you check through Qemu list archieve, you shall see that there were
> more or less similar question: parallelization of Qemu.
> Most of the answers are: it can be hardly done. AFAIK, this is due
> to how dynamic translation is done... you need (most of the part I
> guess) almost 100% serialization.
I completely disagree.
Dynamic translation doesn't need 100% serialisation, but to relax that
it does require atomic ops and memory barriers (including implied
ones) in the guest to be translated to equivalents in the host.
Unfortunately x86 instructions imply a lot of barriers
(program-ordered writes), which is great for programming x86 but not
great when translating to non-x86 host code.
Right now, though, qemu's translator does not do that, even for
x86->x86, so it has to be serialised when running multi-CPU guest code.
KVM, on the other hand, does not do dynamic translation and can run
multiple threads in parallel because the atomic/barrier semantics are
preserved exactly. KVM would be a fine candidate for running multiple
threads on different host machines.
You'd need to serialise memory using page faults, but such techniques
are already implemented with cluster filesystems and writable-mmap'd
files, so it might be possible to use KVM over that.
-- Jamie
next prev parent reply other threads:[~2009-11-16 22:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 14:29 [Qemu-devel] QEMU redesigned for MPI (Message Passing Interface) Victor Vasilchenko
2009-11-16 9:01 ` Mulyadi Santosa
2009-11-16 22:57 ` Jamie Lokier [this message]
2009-11-16 17:55 ` Anthony Liguori
2009-11-17 12:20 ` Paul Brook
2009-11-17 13:40 ` Avi Kivity
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=20091116225722.GF12063@shareable.org \
--to=jamie@shareable.org \
--cc=mulyadi.santosa@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=vvasilchenko@gmail.com \
/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).