From: Gaurav Sharma <gauravs.2010@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Queries on dataplane mechanism
Date: Tue, 28 Jun 2016 14:36:41 +0530 [thread overview]
Message-ID: <CABiB5K4FvxkhGhKed6HYjvDSR0GDCmGDBLe-u=oxeXBawQ-fhA@mail.gmail.com> (raw)
In-Reply-To: <20160624101506.GI9558@stefanha-x1.localdomain>
Hi Stefan,
I am working on something to move PCI devices to data plane architecture.
Do you know any know reasons, as to why this was not tried before ?
Regards,
On Fri, Jun 24, 2016 at 3:45 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Thu, Jun 23, 2016 at 08:56:34PM +0530, Gaurav Sharma wrote:
> > Hi,
> > I am trying to explore how the data plane mechanism works in QEMU. I
> > understand the behavior of QEMU big lock. Can someone clarify the
> following
> > w.r.t. to data plane :
> >
> > 1. Currently only virtio-blk-pci and virtio-scsi-pci have data plane
> > enabled ?
>
> Yes.
>
> > 2. From qemu 2.1.0 data plane is enabled by default.
>
> No "enabled by default" would mean that existing QEMU command-lines
> enable dataplane. This is not the case. You have to explicitly define
> an iothread object and then associate a virtio-blk/virtio-scsi device
> with it.
>
> > I specify the
> > following options in the command line to enable :
> > -enable-kvm -drive if=none,id=drive1,file=file_name -object
> > iothread,id=iothread2 -device
> > virtio-blk-pci,id=drv0,drive=drive1,iothread=iothread2
> > Is the above syntax correct ?
>
> Yes.
>
> > 3. What is the best possible scenario to test data plane ? Currently, I
> > have a test set up wherein i have two different devices [dev1 and dev2].
> If
> > i process a write to dev1 which i made blocking by putting a sleep
> > statement, will i be able to process write on dev2 ? My understanding is
> > that as in case of dataplane we have a different event loop, i should be
> > able to process write on dev2. Is this correct ?
>
> Dataplane improves scalability for high IOPS workloads when there are
> multiple disks.
>
> You do not need to modify any code in order to benchmark dataplane. Run
> fio inside an SMP 4 guest with 4 disks (you can use the host Linux
> kernel's null_blk driver) and you should find that QEMU without
> dataplane has lower iops. The difference should become clear around 4
> or 8 vcpus/disks.
>
> Stefan
>
next prev parent reply other threads:[~2016-06-28 9:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 15:26 [Qemu-devel] Queries on dataplane mechanism Gaurav Sharma
2016-06-24 10:15 ` Stefan Hajnoczi
2016-06-28 9:06 ` Gaurav Sharma [this message]
2016-07-15 14:17 ` Stefan Hajnoczi
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='CABiB5K4FvxkhGhKed6HYjvDSR0GDCmGDBLe-u=oxeXBawQ-fhA@mail.gmail.com' \
--to=gauravs.2010@gmail.com \
--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 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).