From: Daniel Sterling <sterling.daniel@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
bloat <bloat@lists.bufferbloat.net>,
Michael Richardson <mcr+ietf@sandelman.ca>
Subject: [Bloat] finally got the proper cake experience (was: Re: openwrt e1000e (was: Re: cake + ipv6))
Date: Fri, 20 Nov 2020 18:25:21 -0500 [thread overview]
Message-ID: <CAJZMiueKff6o4-XJQUN2L9iTbVnLxryaEF9XM4YAWjO1-C-dHQ@mail.gmail.com> (raw)
In-Reply-To: <CAJZMiucR=2sD0YNrh5PbJX4338Zspi1yHh5yxidPNQQFt-BQ1A@mail.gmail.com>
On Tue, Nov 17, 2020 at 7:00 PM Daniel Sterling
<sterling.daniel@gmail.com> wrote:
> Wanted to give an update on this. All my issues (odd latency, slow
> throughput, etc) went away when I switched from the in-kernel e1000e
> driver to Intel's NAPI driver.
OK y'all, after switching to this driver, I configured my openwrt
snapshot setup as follows:
** e1000e loaded with InterruptThrottleRate=0:
rmmod r8169 ; modprobe r8169
rmmod e1000e ; insmod e1000e InterruptThrottleRate=0
** All ethtool -K offloading turned off:
rx tx sg tso gso gro all off
** flow control / pause frames turned off:
autoneg off rx off tx off
** ring buffers set to smallest setting:
rx 64 tx 64
** byte queue limits set to 3000
echo 3000 > /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/net/eth1/queues/tx-0/byte_queue_limits/limit_max
echo 3000 > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/net/eth0/queues/tx-0/byte_queue_limits/limit_max
cake configured with besteffort and no bandwidth limit:
/usr/sbin/tc qdisc add dev $WAN handle 1: root cake besteffort
internet nat egress ack-filter dual-srchost ethernet
/usr/sbin/tc qdisc add dev $LAN handle 1: root cake besteffort
internet ingress dual-dsthost ethernet
AND ALL MY LATENCY IS GONE.
I've finally experienced the Zen of low latency and high throughput of
the Promised Cake.
This is amazing.
Previously, I was able to get low latency by setting the cake
"bandwidth" setting to about 40-50mbps out of the LAN interface.
Higher than that and I'd see latency.
But now, I can run as fast as the wifi / wired connections allow with
no latency anywhere on the network. This is truly wild.
Why did no one tell me I didn't need that bandwidth setting?? I
finally pushed and pushed and messed with things until I got it
working this way. If this is the intended final configuration, it
needs to be proselytized! Truly wire-line speed and no latency. This
is just, there are no words. The dream is real
Enormous thank you to everyone who worked on cake!
Thanks,
Dan
prev parent reply other threads:[~2020-11-20 23:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 1:52 [Bloat] cake + ipv6 Daniel Sterling
2020-08-18 2:28 ` Jonathan Morton
2020-08-18 2:54 ` Kenneth Porter
[not found] ` <D7DF629BCBA6767D1E78A973@172.27.17.193>
2020-08-18 3:44 ` Daniel Sterling
2020-08-18 4:15 ` Jonathan Morton
2020-08-18 6:41 ` Sebastian Moeller
2020-08-18 14:17 ` Y
2020-08-18 21:55 ` Michael Richardson
2020-09-23 17:36 ` Daniel Sterling
2020-09-23 18:13 ` Jonathan Morton
2020-09-24 1:07 ` Daniel Sterling
2020-09-28 6:22 ` Daniel Sterling
2020-09-28 15:14 ` Toke Høiland-Jørgensen
2020-10-01 5:09 ` Daniel Sterling
2020-10-01 11:59 ` Toke Høiland-Jørgensen
2020-11-18 0:00 ` [Bloat] openwrt e1000e (was: Re: cake + ipv6) Daniel Sterling
2020-11-20 23:25 ` Daniel Sterling [this message]
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=CAJZMiueKff6o4-XJQUN2L9iTbVnLxryaEF9XM4YAWjO1-C-dHQ@mail.gmail.com \
--to=sterling.daniel@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=mcr+ietf@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