Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Tom Gundersen <teg@jklm.no>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SQM in mainline openwrt, fq_codel considered for fedora default
Date: Tue, 21 Oct 2014 12:51:54 -0700	[thread overview]
Message-ID: <CAA93jw7LNHgx=KG9TG1zigiO3TpnKqhsvzfmtz5dHwa11mtQAA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6czXesrundKe2_QrUeJRPkm-Rxmg=S3YnR2uoxc1Km6A@mail.gmail.com>

> http://snapon.lab.bufferbloat.net/~d/beagle_bql/bql_makes_a_difference.png
>
> You can see that BQL makes the most difference in the latency.

And ALSO that these fixes also improved system throughput enormously.
This is partially due to the improvement in ack clocking you get from
reduced RTTs, partially due to improved cache behavior (shorter
queues), and partially continual improvements elsewhere in the tcp
portions of the stack.

With more recent kernels...

I now get full throughput from the beagles in both directions with the
3.16 kernel,
the stil out of tree bql patch, and either fq or fq_codel. I haven't
got around to plotting all those results (they are from kathie's new
lab), but they are here:
http://snapon.lab.bufferbloat.net/~d/pollere/

There is a small buffered tail dropping switch in the way, on these
later data sets. There was some puzzling behavior on the e1000e that I
need to poke into in a more controlled setting.

As for other tunables on hosts, TCP small queues might be amiable to
some tuning, but that too may well evolve further in kernelspace.

-- 
Dave Täht

http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks

  reply	other threads:[~2014-10-21 19:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 18:56 Dave Taht
2014-10-17 19:30 ` Valdis.Kletnieks
2014-10-20 17:03   ` Dave Taht
2014-10-20 17:41     ` Valdis.Kletnieks
2014-10-21 14:50       ` Michal Schmidt
2014-10-21 16:27         ` Valdis.Kletnieks
2014-10-21 16:57           ` Dave Taht
2014-10-21 17:05             ` Michal Schmidt
2014-10-21 17:24               ` Tom Gundersen
2014-10-21 17:44                 ` Michal Schmidt
2014-10-21 17:52                   ` David Personette
2014-10-21 18:00                   ` Michal Schmidt
2014-10-21 18:06                   ` Tom Gundersen
2014-10-21 19:21                     ` Dave Taht
2014-10-21 19:51                       ` Dave Taht [this message]
2014-10-21 20:59                         ` Dave Taht
2014-12-04 16:09                           ` Tom Gundersen
2014-12-04 18:24                             ` Dave Taht
2014-10-21 23:18                 ` Toke Høiland-Jørgensen
2014-12-04 15:05                   ` Tom Gundersen
2014-12-04 15:08                     ` Toke Høiland-Jørgensen

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/cerowrt-devel.lists.bufferbloat.net/

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

  git send-email \
    --in-reply-to='CAA93jw7LNHgx=KG9TG1zigiO3TpnKqhsvzfmtz5dHwa11mtQAA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=teg@jklm.no \
    /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