Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
From: Wei Wang <wei.w.wang at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] SPDK Euro Meeting 11/12: vhost-user target with vvu support
Date: Mon, 17 Dec 2018 18:30:03 +0800	[thread overview]
Message-ID: <5C177AAB.4000000@intel.com> (raw)
In-Reply-To: CAJSP0QWUS_JAg_670g-8Z5nBmQMur=HG1VQ7kkLFFb=DcseKdw@mail.gmail.com

[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]

On 12/14/2018 07:00 PM, Stefan Hajnoczi wrote:
> On Thu, Dec 13, 2018 at 12:22 AM Nikos Dragazis
> <ndragazis(a)outlook.com.gr> wrote:
>> These are all solved by a special virtio device called
>> “virtio-vhost-user”. This device was created by Stefan Hajnoczi and is
>> described here:
>> https://wiki.qemu.org/Features/VirtioVhostUser
> Hi Nikos,
> Nice that you're pushing virtio-vhost-user.  I'm focussed on other
> projects and probably won't resume virtio-vhost-user work any time
> soon.  It was done as part of the vhost-pci effort that Wei Wang from
> Intel was pursuing, so I've CCed them.
>
> Although virtio-vhost-user may have been stalled, I still think it's a
> good solution for device emulation inside VMs.
>
> With some effort virtio-vhost-user can get upstream into the VIRTIO
> specification, QEMU, and SPDK.  A starting point would be to resend
> the VIRTIO spec, QEMU, SPDK patches.  The VIRTIO spec is here:
> https://stefanha.github.io/virtio/vhost-user-slave.html#x1-2830007
>
> If I remember correctly, most of the remaining work was in SPDK/DPDK,
> where the vhost-user library may need refactoring.  I have CCed
> Dariusz, who was working on a general rte_vhost library overhaul and
> had already looked at virtio-vhost-user.
>

It seems Nikos wasn't included in the email, have him cc-ed

Agree with Stefan that virtio-vhost-user is a good inter-VM 
communication solution.
With the previous Vhost-PCI PoC, the 2 VM networking communication (64B 
packet)
throughput is around 1.6x larger than the exiting OVS based solution. 
The data path of
virtio-vhost-user remains the same as Vhost-PCI, so we would also expect 
it to have a
similar good performance.

Btw, could you guys share your usage of this inter-VM communication 
solution in the
storage domain?

Best,
Wei

             reply	other threads:[~2018-12-17 10:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 10:30 Wei Wang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-09-28  2:06 [SPDK] SPDK Euro Meeting 11/12: vhost-user target with vvu support wuzhouhui
2018-12-18 17:22 Nikos Dragazis
2018-12-18 15:36 Nikos Dragazis
2018-12-14 11:00 Stefan Hajnoczi
2018-12-13  0:22 Nikos Dragazis

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=5C177AAB.4000000@intel.com \
    --to=spdk@lists.01.org \
    /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