From: Rick Jones <rick.jones2@hp.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Codel] [Bloat] better testing, linux 3.6.1, cerowrt credits, other stuff
Date: Wed, 10 Oct 2012 16:32:54 -0700 [thread overview]
Message-ID: <507605A6.1010704@hp.com> (raw)
In-Reply-To: <87mwzvphf1.fsf@toke.dk>
On 10/09/2012 12:35 PM, Toke Høiland-Jørgensen wrote:
> I assume that by "infrastructure" you mean "(netperf) servers far away"? What
> would be needed for a test server in terms of resources (bandwidth and
> otherwise)? I could try and persuade my university to let me setup a
> test server on their network (which is in Denmark)...
Keep in mind that netperf needs two open ports - one for the control
connection and one for the data connection.
As far as an access control mechanism goes, it is pretty lame, but the
2.6.0 and later versions of netperf/netserver include the ability to
define a passphrase the netserver must see from netperf before it will
allow a test to be run. It is the global -Z option.
http://www.netperf.org/svn/netperf2/tags/netperf-2.6.0/Release_Notes
happy benchmarking,
rick jones
prev parent reply other threads:[~2012-10-10 23:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-09 3:21 [Codel] " Dave Taht
2012-10-09 14:31 ` Toke Høiland-Jørgensen
2012-10-09 16:45 ` Rick Jones
2012-10-09 18:28 ` [Codel] [Bloat] " Dave Taht
[not found] ` <87mwzvphf1.fsf@toke.dk>
2012-10-09 20:05 ` Rick Jones
2012-10-10 23:27 ` Michael Richardson
2012-10-10 23:29 ` Stephen Hemminger
2012-10-10 23:55 ` Luigi Rizzo
2012-10-10 23:32 ` Rick Jones [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=507605A6.1010704@hp.com \
--to=rick.jones2@hp.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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