From: Daniel Lezcano <dlezcano@fr.ibm.com>
To: xen-devel@lists.xensource.com
Subject: network virtualization performances
Date: Wed, 02 May 2007 21:53:10 +0200 [thread overview]
Message-ID: <4638EC26.4010209@fr.ibm.com> (raw)
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.
Regards.
-- Daniel
next reply other threads:[~2007-05-02 19:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-02 19:53 Daniel Lezcano [this message]
2007-05-04 1:16 ` network virtualization performances Herbert Xu
2007-05-06 20:37 ` Daniel Lezcano
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=4638EC26.4010209@fr.ibm.com \
--to=dlezcano@fr.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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.