From: Tyler Bletsch <tkbletsc@ncsu.edu>
To: kvm@vger.kernel.org
Subject: Support for direct inter-VM sockets? Inter-VM shared memory?
Date: Thu, 20 May 2010 15:19:25 -0400 [thread overview]
Message-ID: <4BF58B3D.2090307@ncsu.edu> (raw)
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?
Apologies if I'm missing some well known doc...I search around google &
the wiki to no avail.
Thanks,
Tyler Bletsch
* http://www.mail-archive.com/kvm-devel@lists.sourceforge.net/msg00304.html
next reply other threads:[~2010-05-20 19:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 19:19 Tyler Bletsch [this message]
2010-05-23 11:11 ` Support for direct inter-VM sockets? Inter-VM shared memory? Avi Kivity
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=4BF58B3D.2090307@ncsu.edu \
--to=tkbletsc@ncsu.edu \
--cc=kvm@vger.kernel.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.