netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Daniel Lezcano <dlezcano@fr.ibm.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Linux Containers <containers@lists.osdl.org>,
	netdev@vger.kernel.org, Dmitry Mishin <dim@openvz.org>
Subject: Re: L2 network namespace benchmarking
Date: Wed, 28 Mar 2007 13:12:03 -0700	[thread overview]
Message-ID: <460ACC13.1080906@hp.com> (raw)
In-Reply-To: <460AC66A.4060606@fr.ibm.com>

> Do you have any pointer to help on benchmarking the network, perhaps a 
> checklist or some scripts for netperf ?

There are some scripts in doc/examples but they are probably a bit long 
in the tooth by now.

The main writeup _I_ have on netperf would be the manual, which was 
recently updated for the 2.4.3 release.

http://www.netperf.org/svn/netperf2/tags/netperf-2.4.3/doc/netperf.html

or the current top of trunk:

http://www.netperf.org/svn/netperf2/trunk/doc/netperf.html

There is also a netperf-talk@netperf.org mailing list which one can join 
and have discussions about netperf, and a netperf-dev@netperf.org if one 
wants to discuss actual netperf (netperf2 or netperf4) development.

rick jones

  reply	other threads:[~2007-03-28 20:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-27 22:16 L2 network namespace benchmarking Daniel Lezcano
2007-03-27 23:08 ` Herbert Poetzl
2007-03-28  7:07   ` Daniel Lezcano
2007-03-28  2:04 ` Eric W. Biederman
2007-03-28  7:49   ` Kirill Korotaev
2007-03-28 12:06     ` Eric W. Biederman
2007-03-28  7:55   ` Daniel Lezcano
2007-03-28 11:52     ` Eric W. Biederman
2007-03-28 18:08       ` Rick Jones
2007-03-28 19:47         ` Daniel Lezcano
2007-03-28 20:12           ` Rick Jones [this message]
2007-03-29  7:37       ` Benjamin Thery
2007-03-29 13:01         ` Eric W. Biederman

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=460ACC13.1080906@hp.com \
    --to=rick.jones2@hp.com \
    --cc=containers@lists.osdl.org \
    --cc=dim@openvz.org \
    --cc=dlezcano@fr.ibm.com \
    --cc=ebiederm@xmission.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).