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/
Home Products Support Community News


[Xen-devel] network virtualization performances

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] network virtualization performances
From: Daniel Lezcano <dlezcano@xxxxxxxxxx>
Date: Wed, 02 May 2007 21:53:10 +0200
Delivery-date: Wed, 02 May 2007 12:52:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Thunderbird (X11/20061107)
Hi all,

I am currently working on the network virtualization for lightweight containers based on the network namespace concept.

The network device list are relative to a namespace, so in one namespace, you can not access to network device belonging to another namespace. To allow the namespace to communicate, a special network device has been written. It is like a "pipe" but for the network with an extremity in each namespace. By this way, the virtualized environment can send traffic via a network device (an extremity of the "pipe") and the traffic goes to the namespace where the real nic is.

During some performance testing, I noticed that using the Gigabyte NIC and netperf, the cpu usage is much more important when the network is virtualized than when not. After investigating, it appears the real NIC is an offload card and when we are using the virtual network device, the offloading is lost and the kernel spends a lot of time to compute checksums and tcp segmentations. That makes sense because the virtual device has not the HW feature like the real NIC.

After looking in internet, I found the "Optimizing Network Virtualization in Xen" document and the problems seems to be exactly the same.

Do you have some pointers, informations about these optimization, specific optimization code or anything else which can help me ?

Thanks you in advance.


  -- Daniel

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>