From: "Benoît Canet" <benoit.canet@irqsave.net>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Benoît Canet" <benoit.canet@irqsave.net>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Dataplane and vhost-blk
Date: Tue, 5 Mar 2013 21:46:30 +0100 [thread overview]
Message-ID: <20130305204629.GA3669@irqsave.net> (raw)
In-Reply-To: <CAJSP0QXULZHuoPmZLSj33-Rh3r7FH+Hgho2FkD9qFJ+uwi2pJw@mail.gmail.com>
> 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.
Benoît
next prev parent reply other threads:[~2013-03-05 21:00 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 [this message]
2013-03-06 10:08 ` Stefan Hajnoczi
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=20130305204629.GA3669@irqsave.net \
--to=benoit.canet@irqsave.net \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.