WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] question about guest-to-guest networking

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] question about guest-to-guest networking
From: Aravind Menon <aravind.menon@xxxxxxx>
Date: Sat, 14 Jan 2006 16:07:48 +0100
Delivery-date: Mon, 16 Jan 2006 11:00:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
As I understand, the network backend driver uses page-remapping to map
packets to be transmitted by the guest domain, and uses page transfer to
transfer page ownership of the packet to be received by the guest
domain.

I was wondering how this would work when one guest domain wanted to
communicate with another guest domain.

The backend driver would remap the packet to be transmitted from the
source guest domain, and then later transfer the ownership of this page
to the target guest domain. However, at the end of transmission, the
source guest domain is notified that it can free the page containing the
network packet.

So, wouldn't this lead to the packet page being owned by the target
domain, while the source domain still believes that it owns the page?

I am referring to a somewhat dated implementation of the network drivers
(Xen version 2.0.6), so I am not aware if this `problem' also exists in
Xen version 3.0.

Any comments or explanations would be helpful.

Thanks,

Aravind



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] question about guest-to-guest networking, Aravind Menon <=