CoDel AQM discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
	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:29:11 -0700	[thread overview]
Message-ID: <20121010162911.5f2d14d4@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <25234.1349911631@sandelman.ca>

On Wed, 10 Oct 2012 19:27:11 -0400
Michael Richardson <mcr@sandelman.ca> wrote:

> 
>     >> But: It became obvious fast that long RTT tests were needed,
>     >> which I've been trying to establish the infrastructure to do
> 
>     toke> I assume that by "infrastructure" you mean "(netperf) servers
>     toke> far away"? What would be needed for a test server in terms of
>     toke> resources (bandwidth and otherwise)? I could try and persuade
>     toke> my university to let me setup a test server on their network
>     toke> (which is in Denmark)...
> 
> I interpret the question to mean networks where is there significant
> actual delay along them.  I seem to recall that there are some ways to
> do this Linux machines, but most commercial test equipment can simulate
> things, including dropping packets.
> I think, however, that we do not want/need and packets dropped, as then
> the bandwidth constraint would not be in the device under test.

netem can do all the stuff commercial gear can.
In fact, it is used by one of the commercial products!

  reply	other threads:[~2012-10-10 23:29 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 [this message]
2012-10-10 23:55           ` Luigi Rizzo
2012-10-10 23:32       ` Rick Jones

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=20121010162911.5f2d14d4@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=mcr@sandelman.ca \
    --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