General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Toke H?iland-J?rgensen <toke@toke.dk>,
	codel@lists.bufferbloat.net, bloat@lists.bufferbloat.net
Subject: Re: [Bloat] [Codel] better testing, linux 3.6.1, cerowrt credits, other stuff
Date: Thu, 11 Oct 2012 01:55:28 +0200	[thread overview]
Message-ID: <20121010235528.GA21987@onelab2.iet.unipi.it> (raw)
In-Reply-To: <20121010162911.5f2d14d4@nehalam.linuxnetplumber.net>

On Wed, Oct 10, 2012 at 04:29:11PM -0700, Stephen Hemminger wrote:
> 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!

similarly you can use ipfw+dummynet, it has been running on
Linux and a variety of other OS for a long time, see

http://info.iet.unipi.it/~luigi/dummynet/

	cheers
	luigi

  reply	other threads:[~2012-10-10 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09  3:21 [Bloat] " Dave Taht
2012-10-09 14:31 ` Toke Høiland-Jørgensen
2012-10-09 16:45   ` [Bloat] [Codel] " Rick Jones
2012-10-09 18:28     ` Dave Taht
2012-10-09 19:35     ` Toke Høiland-Jørgensen
2012-10-09 20:05       ` Rick Jones
2012-10-10 14:27         ` Toke Høiland-Jørgensen
2012-10-10 23:27       ` Michael Richardson
2012-10-10 23:29         ` Stephen Hemminger
2012-10-10 23:55           ` Luigi Rizzo [this message]
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/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121010235528.GA21987@onelab2.iet.unipi.it \
    --to=rizzo@iet.unipi.it \
    --cc=bloat@lists.bufferbloat.net \
    --cc=codel@lists.bufferbloat.net \
    --cc=shemminger@vyatta.com \
    --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