All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "V." <mail@winaoe.org>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	QEMU <qemu-devel@nongnu.org>
Subject: Re: [PATCH/RFC 0/1] Vhost User Cross Cable: Intro
Date: Tue, 14 Jan 2020 10:20:09 +0000	[thread overview]
Message-ID: <CAJSP0QW6cC=rCTn--vJ84t+LzeFND_SeN76CdF1fv6-F4NVDyg@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1CLzR7Q7ei550d+2GhnmcwiGpb2ixem_tr4QUPnsF_KPKg@mail.gmail.com>

On Fri, Jan 10, 2020 at 10:34 AM Marc-André Lureau
<marcandre.lureau@gmail.com> wrote:
> On Wed, Jan 8, 2020 at 5:57 AM V. <mail@winaoe.org> wrote:

Hi V.,
I think I remember you from Etherboot/gPXE days :).

> > 3.
> > Now if Cross Cable is actually a new and (after a code-rewrite of 10) a viable way to connect 2 QEMU's together, could I actually
> > suggest a better way?
> > I am thinking of a '-netdev vhost-user-slave' option to connect (as client or server) to a master QEMU running '-netdev vhost-user'.
> > This way there is no need for any external program at all, the master can have it's memory unshared and everything would just work
> > and be fast.
> > Also the whole thing can fall back to normal virtio if memory is not shared and it would even work in pure usermode without any
> > context switch.
> >
> > Building a patch for this idea I could maybe get around to, don't clearly have an idea how much work this would be but I've done
> > crazier things.
> > But is this is something that someone might be able to whip up in an hour or two? Someone who actually does have a clue about vhost
> > and virtio maybe? ;-)
>
> I believe https://wiki.qemu.org/Features/VirtioVhostUser is what you
> are after. It's still being discussed and non-trivial, but not very
> active lately afaik.

virtio-vhost-user is being experimented with in the SPDK community but
there has been no activity on VIRTIO standardization or the QEMU
patches for some time.  More info here:
https://ndragazis.github.io/spdk.html

I think the new ivshmem v2 feature may provide the functionality you
are looking for, but I haven't looked at them yet.  Here is the link:
https://www.mail-archive.com/qemu-devel@nongnu.org/msg668749.html

And here is Jan's KVM Forum presentation on ivshmem v2:
https://www.youtube.com/watch?v=TiZrngLUFMA

Stefan


  reply	other threads:[~2020-01-14 10:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  1:54 [PATCH/RFC 0/1] Vhost User Cross Cable: Intro V.
2020-01-10 10:27 ` Marc-André Lureau
2020-01-14 10:20   ` Stefan Hajnoczi [this message]
2020-02-13 13:48     ` Nikos Dragazis
2020-02-21 10:44       ` Stefan Hajnoczi
2020-02-13 14:50 ` Michael S. Tsirkin

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='CAJSP0QW6cC=rCTn--vJ84t+LzeFND_SeN76CdF1fv6-F4NVDyg@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=mail@winaoe.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.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 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.