All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: Linux Containers <containers@lists.osdl.org>,
	Linux Netdev List <netdev@vger.kernel.org>,
	Benjamin Thery <benjamin.thery@bull.net>
Subject: Re: network namespace ipv6 perfs
Date: Mon, 03 Mar 2008 11:38:49 -0800	[thread overview]
Message-ID: <47CC53C9.1000400@hp.com> (raw)
In-Reply-To: <47CC0920.6000005@fr.ibm.com>

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?

 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?

happy benchmarking,

rick jones

> 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 :)
> 

  parent reply	other threads:[~2008-03-03 19:38 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
2008-03-03 14:48 ` Benjamin Thery
2008-03-03 19:38 ` Rick Jones [this message]
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=47CC53C9.1000400@hp.com \
    --to=rick.jones2@hp.com \
    --cc=benjamin.thery@bull.net \
    --cc=containers@lists.osdl.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.