All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Tyler Bletsch <tkbletsc@ncsu.edu>
Cc: kvm@vger.kernel.org, Cam Macdonell <cam@cs.ualberta.ca>
Subject: Re: Support for direct inter-VM sockets?  Inter-VM shared memory?
Date: Sun, 23 May 2010 14:11:29 +0300	[thread overview]
Message-ID: <4BF90D61.40206@redhat.com> (raw)
In-Reply-To: <4BF58B3D.2090307@ncsu.edu>

On 05/20/2010 10:19 PM, Tyler Bletsch wrote:
> I'm interested in moving some research prototypes from Xen to KVM, but 
> there are a few esoteric features I'd need to do this.
>
> First is an efficient mechanism for direct VM-to-VM 
> sockets...something that bypasses the protocol stack and minimizes 
> overhead.  Xen has XenSocket, XenLoop, and others.  I found a few 
> mentions of this idea dating back to 2006*, mostly saying that a few 
> people have done something like this as a one-off, but nothing 
> official has been released.  I haven't found anything like this more 
> recently, though.  Has there been any progress on this front?  
> Ideally, I'd want a character device or a special program that acts as 
> a fast pipe to a different VM.
>
> Second, what about inter-VM shared memory?

Inter-VM shared memory (contributed by Cam, copied) is in the process of 
being merged.  That includes a fast interguest interrupt mechanism 
(using irqfd), so you could easily layer a fast interguest pipe on top 
of that.

It's possible to do a dedicated guest-to-guest channel using virtio and 
a dma engine, but I'm not aware of any efforts in that direction.

-- 
error compiling committee.c: too many arguments to function


      reply	other threads:[~2010-05-23 11:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-20 19:19 Support for direct inter-VM sockets? Inter-VM shared memory? Tyler Bletsch
2010-05-23 11:11 ` Avi Kivity [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=4BF90D61.40206@redhat.com \
    --to=avi@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --cc=kvm@vger.kernel.org \
    --cc=tkbletsc@ncsu.edu \
    /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.