From: Dave Taht <dave.taht@gmail.com>
To: Tobias Diedrich <ranma+openwrt@tdiedrich.de>
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: Mon, 21 May 2012 04:48:34 +0100 [thread overview]
Message-ID: <CAA93jw7S9CoWGYOXDZ=M_ajkNi0mEeO-5fcw2e-4fz0vK0p+fw@mail.gmail.com> (raw)
In-Reply-To: <20120521003115.GO22418@yumi.tdiedrich.de>
Thx for the numbers!
Could you do a TCP_RR while under load from UDP_STREAM?
On Mon, May 21, 2012 at 1:31 AM, Tobias Diedrich
<ranma+openwrt@tdiedrich.de> wrote:
> Tobias Diedrich wrote:
>> Dave Taht wrote:
>> > In looking over the enormous stack of boards and drivers that openwrt
>> > supports, I see that many of the ethernet drivers don't yet support
>> > Linux 3.3's "Byte Queue Limits", which are discussed here:
>> >
>> > http://lwn.net/Articles/454390/
>> >
>> > It would be good if more did. They improve network performance in the
>> > general case enormously, particularly when a link is not connected at
>> > it's peak wire speed.
>> >
>> > *Adding* support for BQL to an ethernet driver is trivial, here's an
>> > example of how.
>>
>> I tried adding BQL to the ramips ethernet driver, however I found
>> some interesting behaviour while doing
>> "root@OpenWrt:~# netperf -l 120 -t UDP_STREAM -H myserver"
>>
>> It looks like the briding code still needs to implement this as well?
>>
>> netperf UDP_STREAM:
>> iface limit_min inflight tx mbps remote mbps ping ms
>> eth0 0 ~15000 95.71 95.71 ~10ms
>> eth0 1000000 ~300000 177.98 23.28(*) ~30ms
>> br0 0 ~15000 154.88 33.94(*) ~120ms
>> br0 1000000 ~300000 170.92 25.57(*) ~30ms
>>
>> (*) bwm-ng on the server showed ~100mbps incoming...
> [...]
>> Haven't tried codel yet...
>
> Turns out, it works nicely with codel, even with the bridge:
>
> netperf: netperf -l 120 -t UDP_STREAM -H myserver
> fq_codel: tc qdisc add dev eth0 handle 1: root fq_codel target 5ms
>
> iface eth0 qdisc bql inflight tx mbps sys time ping ms
> eth0 pfifo_fast no n/a 182.98(*) 96.43s ~30ms
> eth0 fq_codel no n/a 177.98(*) 96.09s ~30ms
> eth0 pfifo_fast yes ~15000 95.71 42.73s ~10ms
> eth0 fq_codel yes ~15000 95.19 51.52s ~4ms
> br0 pfifo_fast yes ~15000 155.19(*) 94.24s ~120ms
> br0 fq_codel yes ~15000 90.92 65.52s ~4ms
>
> (*) 100mbit link after the switch, ifconfig eth0 shows no drops,
> so I'm assuming they are getting dropped by the switch.
>
> --
> Tobias PGP: http://8ef7ddba.uguu.de
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
next parent reply other threads:[~2012-05-21 3:48 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 [this message]
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
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='CAA93jw7S9CoWGYOXDZ=M_ajkNi0mEeO-5fcw2e-4fz0vK0p+fw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=openwrt-devel@lists.openwrt.org \
--cc=ranma+openwrt@tdiedrich.de \
/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