From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tyler Bletsch Subject: Support for direct inter-VM sockets? Inter-VM shared memory? Date: Thu, 20 May 2010 15:19:25 -0400 Message-ID: <4BF58B3D.2090307@ncsu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from uni13mr.unity.ncsu.edu ([152.1.224.171]:42315 "EHLO uni13mr.unity.ncsu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751915Ab0ETTTP (ORCPT ); Thu, 20 May 2010 15:19:15 -0400 Received: from [152.14.92.53] (maridia.csc.ncsu.edu [152.14.92.53]) by uni13mr.unity.ncsu.edu (8.13.8/8.13.8/Nv5.2010.0329) with ESMTP id o4KJJEIs013196 for ; Thu, 20 May 2010 15:19:14 -0400 (EDT) Sender: kvm-owner@vger.kernel.org List-ID: 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