From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Wang, Wei W" <wei.w.wang@intel.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vhost-pci and virtio-vhost-user
Date: Mon, 15 Jan 2018 14:02:57 +0000 [thread overview]
Message-ID: <20180115140257.GH13238@stefanha-x1.localdomain> (raw)
In-Reply-To: <286AC319A985734F985F78AFA26841F7393CA35E@shsmsx102.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
On Sun, Jan 14, 2018 at 03:36:19AM +0000, Wang, Wei W wrote:
> On Friday, January 12, 2018 6:38 PM, Stefan Hajnoczi wrote:
> > On Fri, Jan 12, 2018 at 02:44:00PM +0800, Wei Wang wrote:
> > > On 01/11/2018 05:56 PM, Stefan Hajnoczi wrote:
> > > > On Thu, Jan 11, 2018 at 6:31 AM, Wei Wang <wei.w.wang@intel.com>
> > wrote:
> > > > > On 01/11/2018 12:14 AM, Stefan Hajnoczi wrote:
> > I think the virtio-vhost-user end result is worth it though: vhost devices like
> > examples/vhost/ and examples/vhost/scsi/ will work with both AF_UNIX and
> > virtio-vhost-user. This makes it simpler for users and vhost device
> > developers - you only have one implementation of net, scsi, blk, etc devices.
>
> For the driver part, isn't it that net, scsi, blk will have their own separate implementation on top of the common libret_vhost?
Yes.
The following DPDK components use librte_vhost:
drivers/net/vhost
examples/tep_termination
examples/vhost
examples/vhost_scsi
They will all be able to use virtio-vhost-user.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2018-01-15 14:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 16:14 [Qemu-devel] vhost-pci and virtio-vhost-user Stefan Hajnoczi
2018-01-11 6:31 ` Wei Wang
2018-01-11 9:56 ` Stefan Hajnoczi
2018-01-12 6:44 ` Wei Wang
2018-01-12 10:37 ` Stefan Hajnoczi
2018-01-14 3:36 ` Wang, Wei W
2018-01-15 14:02 ` Stefan Hajnoczi [this message]
2018-01-11 10:57 ` Jason Wang
2018-01-11 15:23 ` Stefan Hajnoczi
2018-01-12 3:32 ` Jason Wang
2018-01-12 5:20 ` Yang, Zhiyong
2018-01-15 3:09 ` Jason Wang
2018-01-12 10:18 ` Stefan Hajnoczi
2018-01-15 6:56 ` Jason Wang
2018-01-15 7:59 ` Wei Wang
2018-01-15 8:34 ` Jason Wang
2018-01-15 10:43 ` Wei Wang
2018-01-16 5:33 ` Jason Wang
2018-01-17 8:44 ` Wei Wang
2018-01-15 13:56 ` Stefan Hajnoczi
2018-01-16 5:41 ` Jason Wang
2018-01-18 10:51 ` Stefan Hajnoczi
2018-01-18 11:51 ` Jason Wang
2018-01-19 17:20 ` Stefan Hajnoczi
2018-01-22 3:54 ` Jason Wang
2018-01-23 11:52 ` Stefan Hajnoczi
2018-01-15 7:56 ` Wei Wang
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=20180115140257.GH13238@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=wei.w.wang@intel.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).