qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: OneSoul <onesoul@autistici.org>
Subject: Re: [Qemu-devel] Qemu + CUDA: a new possible way?
Date: Sat, 6 Jun 2009 03:42:33 +0100	[thread overview]
Message-ID: <200906060342.33783.paul@codesourcery.com> (raw)
In-Reply-To: <4A297B77.8080008@autistici.org>

> Recently, reading some technical articles over internet, I have
> discoverd the big potentialities of the CUDA framework in relation to
> the scientific and graphic computing that takes strong advantage from
> the most recent GPUs. Someone has used it for password recovery,
> realtime rendering, etc, with great results.

Most of these problems are what's known as embarrassingly parallel. It's 
trivial to split them up into many small independent pieces. A GPU contains 
hundreds or thousands of small, loosely coupled, low power processing units so 
is a good fit for this kind of problem.

Most of the work that qemu does is completely the opposite. Every step is 
highly dependent on the preceding steps, so you have to execute them in 
series.

If you really think you have figured our some magic way around this then your 
first step should be to make qemu work over a small number (say 8 or 16) of 
tightly coupled CPU cores. If you can't do that then you haven't got a hope in 
hell of making it work over a vast number of remote GPU cores.

Paul

  parent reply	other threads:[~2009-06-06  2:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 20:09 [Qemu-devel] Qemu + CUDA: a new possible way? OneSoul
2009-06-05 20:59 ` Lennart Sorensen
2009-06-05 21:31 ` Blue Swirl
2009-06-06  2:42 ` Paul Brook [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-05  8:01 OneSoul

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=200906060342.33783.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=onesoul@autistici.org \
    --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).