CoDel AQM discussions
 help / color / mirror / Atom feed
From: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
To: Rick Jones <rick.jones2@hp.com>
Cc: OpenWrt Development List <openwrt-devel@lists.openwrt.org>,
	codel@lists.bufferbloat.net
Subject: Re: [Codel] BQL support in Ethernet drivers (and Kathie Nichols and Van Jacobson's new AQM, codel)
Date: Tue, 22 May 2012 01:09:50 +0200	[thread overview]
Message-ID: <20120521230950.GB28713@yumi.tdiedrich.de> (raw)
In-Reply-To: <4FBABEF8.7050002@hp.com>

Rick Jones wrote:
> On 05/21/2012 02:49 PM, Tobias Diedrich wrote:
> >Rick Jones wrote:
> >>On 05/20/2012 08:48 PM, Dave Taht wrote:
> >>>Thx for the numbers!
> >>>
> >>>Could you do a TCP_RR while under load from UDP_STREAM?
> >>
> >>If you want to generate pretty pictures while doing so, you can
> >>probably tweak
> >>http://www.netperf.org/svn/netperf2/trunk/doc/examples/bloat.sh
> >
> >How about this:
> >http://tdiedrich.de/~ranma/bufferbloat-rt3050/
> 
> They look pretty I suppose, but it also looks like I've got the
> vrules botched somehow.  Though I cannot find the bug just yet in
> the repository copy.  The red vertical line should be at the start
> of the UDP_STREAM test's results, and there should be a black one
> right after.  They shouldn't be at the ends of the _RR test.  Did
> you tweak that bit when you converted to a UDP_STREAM test?

Ah, yes, I botched the vrules.

> The other thing is it appears the scaling to make rrdtool look like
> it supports dual y-axes could use a bit of tweaking.  I was pretty
> much guessing there :(

Well, I tweaked the scaling myself since I wasn't happy with the
original result either. :)

I reuploaded new images with correct vrules and your scaling.

Anything above 100Mbit can be assumed to be dropped here (although
only the bridge seems to drop, the gige mac gets backpressure from
the switch I think and just delays transmitting the next packet I
suppose).

I can do a TCP_STREAM test, but since the SoC lacks sufficient oomph
to saturate a 100Mbit link the results are going to be boring I
expect. I get about 3MiB/s, regardless of TCP_STREAM or TCP_SENDFILE.
Maybe TCP_SENDFILE would be a bit faster if the driver implemented
checksum offload.

-- 
Tobias						PGP: http://8ef7ddba.uguu.de

  parent reply	other threads:[~2012-05-21 23:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAA93jw6TcZGpxpS=DhuHCTWBn3uq1RbzugtJ3oJmA5zx9oDP-w@mail.gmail.com>
     [not found] ` <20120520212944.GK22418@yumi.tdiedrich.de>
     [not found]   ` <20120521003115.GO22418@yumi.tdiedrich.de>
2012-05-21  3:48     ` Dave Taht
2012-05-21 17:24       ` Rick Jones
2012-05-21 21:49         ` Tobias Diedrich
2012-05-21 22:17           ` Rick Jones
2012-05-21 22:20             ` Rick Jones
2012-05-21 23:09             ` Tobias Diedrich [this message]
2012-05-21 23:30               ` Rick Jones
2012-05-22  1:22                 ` Rick Jones
2012-05-22  1:29                   ` Dave Taht
2012-05-22  0:27           ` Dave Taht
2012-05-29 13:00             ` Tobias Diedrich

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=20120521230950.GB28713@yumi.tdiedrich.de \
    --to=ranma+openwrt@tdiedrich.de \
    --cc=codel@lists.bufferbloat.net \
    --cc=openwrt-devel@lists.openwrt.org \
    --cc=rick.jones2@hp.com \
    /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