All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Yuan <namei.unix@gmail.com>
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: Wed, 06 Mar 2013 11:23:48 +0800	[thread overview]
Message-ID: <5136B6C4.7040509@gmail.com> (raw)
In-Reply-To: <CAJSP0QXULZHuoPmZLSj33-Rh3r7FH+Hgho2FkD9qFJ+uwi2pJw@mail.gmail.com>

On 03/05/2013 11:59 PM, Stefan Hajnoczi wrote:
>> I am looking for a way to help improving qemu block performance.
>> >
>> > APIC-V is a work in progress and the two options with public code are vhost-*
>> > and virtio-blk-dataplane.
>> >
>> > The way of doing seems very similar (bypassing the qemu lock) and dedicating
>> > a thread to each emulated virtio block device.
>> >
>> > vhost-* is in kernel while dataplane is in qemu.
> Yes, they take a similar approach.  The main difference is using a
> vhost kernel thread versus a QEMU userspace thread.
> 

The other merit of blk-dataplane over in-kernel vhost_blk that I can
think of, is underlying various protocols such as Sheepdog would benefit
from it without adding code, assuming the final goal of blk-dataplain is
fully fulfilled that aims to be integrated into QEMU block layer. For
vhost_blk, ony local backing file will benefit from it without adding
more code in the kernel.

Thanks,
Yuan

      parent reply	other threads:[~2013-03-06  3:24 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
2013-03-06  3:23   ` Liu Yuan [this message]

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=5136B6C4.7040509@gmail.com \
    --to=namei.unix@gmail.com \
    --cc=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.