netdev - Re: network namespace ipv6 perfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <47CD71FC.6010504@bull.net>
Date:	Tue, 04 Mar 2008 16:59:56 +0100
From:	Benjamin Thery <benjamin.thery@...l.net>
To:	Rick Jones <rick.jones2@...com>
Cc:	Daniel Lezcano <dlezcano@...ibm.com>,
	Linux Containers <containers@...ts.osdl.org>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: network namespace ipv6 perfs

Daniel Lezcano wrote:
> Rick Jones 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.
>>
>> The *_RR tests seem to show a drop in througput and corresponding 
>> increases in service demand - could that be because things like TSO et 
>> al cannot mask much of anything in the way of a path-length increase?
> 
> Hmm. In fact Benjamin took the 2.6.23.16 kernel where there were no 
> network namespace code at all. So these differences between 2.6.23.16 
> and 2.6.25-rc1 does not show a performance degradation especially 
> related to the network namespaces. The important point is the 2.6.25-rc1 
> without ipv6 netns and 2.6.25-rc1 with ipv6 netns code applied, I mean 
> the second and the third line and we can point that the ipv6 netns code 
> does not degrade performances for either throughput and service demand.

As Daniel stated, we should not compare the first bar with the other
ones directly. May be I should have arranged the chart differently and
made it more clear that the first bar is "2.6.23 vanilla" and the second
one is "2.6.25-rc1 vanilla". Many changes happened in the whole kernel
between 2.6.23 and 2.6.24 so we can't compare the first two bars to tell
if network namespace degraded performances (and only a small part of
netns is in 2.6.24).
The way I presented the chart is a bit misleading. :)

What's interesting to compare in the charts is the 2nd, 3rd and 4th
lines. It shows that on the exact same hardware (in the 4th case the
physical interface is moved into the child namespace), with or without
the patchset, using network namespace or not, performance is about the
same.

Benjamin

>>  From the annotations, I'm ass-u-me-ing that NS was only used on the 
>> netperf side and not both netperf and netserver side?
> 
> right :)
> 
>> happy benchmarking,
> 
> Thanks Rick.
> 
>   -- Daniel
> 
> 


-- 
B e n j a m i n   T h e r y  - BULL/DT/Open Software R&D

    http://www.bull.com
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html