qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Dataplane and vhost-blk
Date: Wed, 6 Mar 2013 11:08:26 +0100	[thread overview]
Message-ID: <20130306100826.GC1954@stefanha-thinkpad.muc.redhat.com> (raw)
In-Reply-To: <20130305204629.GA3669@irqsave.net>

On Tue, Mar 05, 2013 at 09:46:30PM +0100, Benoît Canet wrote:
> > You need to set a more specific goal.  Some questions to get started:
> >  * Which workloads do you care about and what are their
> > characteristics (sequential or random I/O, queue depth)?
> >  * Do you care about 1 vcpu guests or 4+ vcpu guests?  (SMP scalability)
> >  * Are you using an image format?
> 
> The usage would be a typical HPC workload: 4 vcpu in SMP and random IO on raw
> devices.

Okay.  If you want to do performance analysis on the existing stack,
then the next step is to choose a benchmark that represents this
workload.  Then you can collect profiles and see where there is room for
improvement.

In virtio-blk data plane world I'm currently converting core QEMU code
to support multiple AioContexts.  This is needed in order to use
BlockDriverStates from threads (without holding the global mutex).  This
is a pretty linear task.

The second half of this work is enabling device emulation code to run in
threads without the global mutex.  The trickiest thing here is probably
guest memory access - making guest memory access and DMA work safely
from a thread.  I haven't really started on this, Ping Fan Liu has
worked on it in the past, you could chat with him to find out the
current status.

Stefan

  reply	other threads:[~2013-03-06 10:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 14:18 [Qemu-devel] Dataplane and vhost-blk Benoît Canet
2013-03-05 15:59 ` Stefan Hajnoczi
2013-03-05 20:46   ` Benoît Canet
2013-03-06 10:08     ` Stefan Hajnoczi [this message]
2013-03-06  3:23   ` Liu Yuan

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=20130306100826.GC1954@stefanha-thinkpad.muc.redhat.com \
    --to=stefanha@gmail.com \
    --cc=benoit.canet@irqsave.net \
    --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).