From: Pavel Emelyanov <xemul@openvz.org>
To: Benjamin Thery <benjamin.thery@bull.net>
Cc: Benjamin Thery <ben.thery@gmail.com>,
Daniel Lezcano <dlezcano@fr.ibm.com>,
Linux Containers <containers@lists.osdl.org>,
Linux Netdev List <netdev@vger.kernel.org>,
Denis Lunev <den@openvz.org>
Subject: Re: [Devel] Re: network namespace ipv6 perfs
Date: Wed, 05 Mar 2008 15:39:02 +0300 [thread overview]
Message-ID: <47CE9466.90101@openvz.org> (raw)
In-Reply-To: <47CC3516.7030901@bull.net>
Benjamin Thery wrote:
> Benjamin Thery wrote:
>> On Mon, Mar 3, 2008 at 3:55 PM, Pavel Emelyanov <xemul@openvz.org> wrote:
>>> Benjamin Thery wrote:
>>> > Daniel Lezcano wrote:
>>> >> Hi,
>>> >>
>>> >> Some performance tests was made by Benjamin to watch out the impact of
>>> >> the network namespace. The good news is there is no impact when used
>>> >> with or without namespaces. That has been checked using a real network
>>> >> device inside a network namespace.
>>> >>
>>> >> These results are consistent with the ones previously made for ipv4.
>>> >>
>>> >> http://lxc.sourceforge.net/network/bench_ipv6_graph.php
>>> >>
>>> >> Thanks to Benjamin who did all the performance tests :)
>>> >
>>> > In these results, may be, there is one thing that should be explained.
>>> > It is the CPU utilization overhead in the 'veth' case.
>>> >
>>> > Compared to physical devices or macvlan, veth interfaces don't benefit
>>> > from hardware offloading mechanisms: i.e. checksums have to be computed
>>> > by the soft. That explains the big overhead in CPU utilization when
>>>
>>> You can tune the veth devices not to account checksum when unnecessary.
>> Oh. This is interesting.
>>
>> You mean with ethtool -K rx/tx?
>> I will give it a try.
>
> Pavel,
>
> I had no luck with "ethtool -K veth0 rx on tx on".
> On my testbed, with these options TCP drops packets
> (trying to establish a ssh connection between init and child namespace).
>
>
> Then, I tested "ethtool -K veth0 rx on tx off".
> This time TCP (and netperf) work, but I see no difference in
> CPU load compared to the case without offloading.
>
> Can I tune veth differently?
Yup. You may try turn tso and sg on as well.
> (BTW, I run netperf between a child namespace on host A and netserv
> on host B. The stream goes through the following interface:
> veth1 on A -> veth0 on A -> eth1 on A -> ("real network") -> eth1 on B)
>
> Benjamin
>
>>> > using this kind of virtual interface.
>>> >
>>> > Benjamin
>>> >
>>> >> Regards
>>> >> -- Daniel
>>> >>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe netdev" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>
>
next prev parent reply other threads:[~2008-03-05 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 14:20 network namespace ipv6 perfs Daniel Lezcano
2008-03-03 14:42 ` Benjamin Thery
2008-03-03 14:55 ` [Devel] " Pavel Emelyanov
2008-03-03 15:04 ` Benjamin Thery
2008-03-03 17:27 ` Benjamin Thery
2008-03-05 12:39 ` Pavel Emelyanov [this message]
2008-03-03 14:48 ` Benjamin Thery
2008-03-03 19:38 ` Rick Jones
2008-03-03 20:01 ` Daniel Lezcano
2008-03-04 15:59 ` Benjamin Thery
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=47CE9466.90101@openvz.org \
--to=xemul@openvz.org \
--cc=ben.thery@gmail.com \
--cc=benjamin.thery@bull.net \
--cc=containers@lists.osdl.org \
--cc=den@openvz.org \
--cc=dlezcano@fr.ibm.com \
--cc=netdev@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.