All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Harris, James R" <james.r.harris@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	"Liu, Changpeng" <changpeng.liu@intel.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Felipe Franciosi <felipe@nutanix.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Marc-Andre Lureau <marcandre.lureau@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 0/4] Introduce vhost-user-scsi and sample application
Date: Thu, 6 Jul 2017 17:03:39 +0000	[thread overview]
Message-ID: <7813DE88-EB6D-4330-AC69-27E7051C4000@intel.com> (raw)
In-Reply-To: <30b1f1cb-f959-7711-96c2-5d5c138135e1@redhat.com>


> On Jul 6, 2017, at 9:56 AM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> 
> 
> 
> On 06/07/2017 18:54, Harris, James R wrote:
>> Hi Michael,
>> 
>> Yes - we (SPDK team at Intel) have this on our TODO list, in addition
>> to a polled mode virtio-scsi driver (akin to the DPDK virtio-net driver that
>> can be used in the guest).
> 
> Can you also look at virtio-blk poll-mode drivers and vhost-user-blk
> (vhost-user-blk would be really easy to write, the sample server being
> much more work than the QEMU code)?
> 
> Paolo

Hi Paolo,

vhost-user-blk:

We have an initial implementation in our SPDK QEMU repo.  Changpeng Liu (added)
will be sending this to the QEMU mailing list shortly.  If you are interested in viewing it
before it hits the mailing list, you can take a look at the patch here:

https://github.com/spdk/qemu/commit/db2fcb0f5002c3d195e756eab07bd976ccf6e7c8

virtio-blk poll-mode driver:

Yes - this is part of our plan as well - once we have virtio-scsi in place, adding virtio-blk
will be relatively straightforward.

Thanks,

-Jim

  reply	other threads:[~2017-07-06 17:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 18:25 [Qemu-devel] [PATCH v5 0/4] Introduce vhost-user-scsi and sample application Felipe Franciosi
2017-03-02 18:25 ` [Qemu-devel] [PATCH v5 1/4] libvhost-user: replace vasprintf() to fix build Felipe Franciosi
2017-03-02 19:28   ` Eric Blake
2017-03-02 18:25 ` [Qemu-devel] [PATCH v5 2/4] vhost-scsi: create a vhost-scsi-common abstraction Felipe Franciosi
2017-03-02 18:25 ` [Qemu-devel] [PATCH v5 3/4] vus: Introduce vhost-user-scsi host device Felipe Franciosi
2017-03-02 18:25 ` [Qemu-devel] [PATCH v5 4/4] vus: Introduce a vhost-user-scsi sample application Felipe Franciosi
2017-03-02 18:31 ` [Qemu-devel] [PATCH v5 0/4] Introduce vhost-user-scsi and " no-reply
2017-03-02 18:32 ` no-reply
2017-03-02 18:46 ` no-reply
2017-03-02 21:47 ` Michael S. Tsirkin
2017-04-21 14:53   ` Felipe Franciosi
2017-07-06 13:41     ` Michael S. Tsirkin
2017-07-06 16:54       ` Harris, James R
2017-07-06 16:56         ` Paolo Bonzini
2017-07-06 17:03           ` Harris, James R [this message]
2017-07-06 17:06             ` Paolo Bonzini
2017-07-06 17:38               ` Harris, James R
2017-07-06 17:11             ` Marc-André Lureau
2017-07-06 17:44               ` Harris, James R

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=7813DE88-EB6D-4330-AC69-27E7051C4000@intel.com \
    --to=james.r.harris@intel.com \
    --cc=berrange@redhat.com \
    --cc=changpeng.liu@intel.com \
    --cc=felipe@nutanix.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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.