From: Victor Vasilchenko <vvasilchenko@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] QEMU redesigned for MPI (Message Passing Interface)
Date: Fri, 13 Nov 2009 14:29:05 +0000 [thread overview]
Message-ID: <747a56b80911130629q4046b4fbg400f7566997aa931@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Good day,
I've got an idea in my head and can't get rid of it - neither can I find any
solution on web.
The idea is to use the Virtualization Software with the purpose OPPOSITE to
it's natural way.
The practical example below will explain it completely:
1) we take 4 common modern computers - CoreQuad + 8 GB Memory.
2) we assemble a standard Linux cluster with 16 cores and 32G memory.
3) and now - we run the only one virtual guest system, but give it ALL
available resources.
The result:
A Virtual PC running on 15 cores and 31Gb of memory (-1 for host OS and VM
software).
Any modern OS installed inside this Virtual PC will utilize all resources in
normal way :
1) the video encoding software will use 15 threads for transcoding
2) the 3D studios (Maya/Max) will use 15 threads and all 31GB memory
3) make -j 15
4) etc.
There is no need to redesign (with MPI MPICH/LAM support) a standard,
currently used programs - they will just work as one would run them on
standard CoreQuad system,
but almost 4 times faster (15cores).
Looks great so far, doesn't it?
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.
[-- Attachment #2: Type: text/html, Size: 1479 bytes --]
next reply other threads:[~2009-11-13 14:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 14:29 Victor Vasilchenko [this message]
2009-11-16 9:01 ` [Qemu-devel] QEMU redesigned for MPI (Message Passing Interface) Mulyadi Santosa
2009-11-16 22:57 ` Jamie Lokier
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=747a56b80911130629q4046b4fbg400f7566997aa931@mail.gmail.com \
--to=vvasilchenko@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).