From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cake latency update
Date: Sun, 12 Feb 2017 17:37:53 +0100 [thread overview]
Message-ID: <ED7C46F3-CBB7-4D71-BFB8-025EDF4C23CD@gmail.com> (raw)
In-Reply-To: <8305DE32-10AB-42C3-8D08-5FF3391914BF@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2961 bytes --]
Or, I can do: ethtool -K eth0 tx off rx off
and disable the checksums entirely. That stops the messages, but unfortunately it doesn’t appear to be the end of the throughput shifts.
But this experience has made me want to look at all of this on other hardware, so that’s next.
> On Feb 12, 2017, at 3:12 PM, Pete Heist <peteheist@gmail.com> wrote:
>
>> On Feb 12, 2017, at 2:08 PM, Dave Taht <dave.taht@gmail.com <mailto:dave.taht@gmail.com>> wrote:
>>
>> Disable offloads on the sky hardware and see what happens?
>>
>> ethtool -K gro off tso off gso off your_device
>
> I’d already had them disabled for testing in /etc/network/interfaces:
>
> post-up ethtool -K eth0 tso off gso off gro off sg off
>
> On a whim I tried _enabling_ offloads again but it happens in both cases.
>
>> How old is the OS on that hardware - offloads have always been tricksy.
>
> Pretty new: Ubuntu 16.10 (GNU/Linux 4.8.0-37-generic x86_64)
>
>> as to why you might be seeing it more with cake, with this stuff on,
>> you are not necessarily checking every packet for checksums, and flows
>> are "finer" - more mixed up packets.
>>
>> capturing these events with tcpdump at various points on the path might help.
>>
>> Still, these are the kinds of baseline deployment issues that block
>> progress elsewhere. The whole first stage of the rocket has to succeed
>> in order to test the second. Doesn't matter how good your second stage
>> is, if you RUD the first.
>
> It must be a challenge for you guys sometimes! Unless I can find an obvious solution soon it’s probably going to mean a hardware change for me. But there are only a few options I see with what’s available to me now:
>
> 1) Using my Apple USB Ethernet adapter for testing instead of just management. Not excited about that- no BQL? USB latency? fq_codel on this adapter over Ethernet reduces Flent RRUL average latency to a pretty solid 1ms, looks sufficient? (Perhaps no coincidence that USB 2.0 start-of-frame is sent every 1 ms.)
>
> 2) Using a 1.25 GHz Mac Mini PPC G4 I have laying around. I successfully ran fq_codel for ADSL on that box in the past, but at 5 / 0.5 Mbps. Accurate Flent results running Cake at 80 Mbps? Timer issues? Also I think no BQL support with the Sun GEM chipset: https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/sun/sungem.c <https://github.com/torvalds/linux/blob/master/drivers/net/ethernet/sun/sungem.c>.
>
> 3) Using two of these for my routers instead: https://pcengines.ch/alix2d2.htm <https://pcengines.ch/alix2d2.htm>, which I’ll want to test later anyway. They’re not new. 500 MHz AMD Geode LX800. Pre-Obama (June 2008). Not even sure yet if I’ll rate limit properly at 80-90 Mbit with these.
>
> Any opinion on a ‘best’ alternative among these? I’m leaning towards #1 for ease. Otherwise I’ll make my way, and may have to dig up some better hardware.
>
> Pete
>
[-- Attachment #2: Type: text/html, Size: 4702 bytes --]
next prev parent reply other threads:[~2017-02-12 16:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 16:36 Pete Heist
2017-02-09 20:52 ` Jonathan Morton
2017-02-10 8:04 ` Pete Heist
2017-02-10 8:49 ` Jonathan Morton
2017-02-10 9:21 ` Pete Heist
2017-02-10 9:29 ` Jonathan Morton
2017-02-10 10:05 ` Pete Heist
2017-02-10 10:31 ` Jonathan Morton
2017-02-10 11:08 ` Pete Heist
2017-02-10 11:35 ` Sebastian Moeller
2017-02-10 12:21 ` Pete Heist
2017-02-12 12:43 ` Pete Heist
2017-02-12 13:08 ` Dave Taht
2017-02-12 14:12 ` Pete Heist
2017-02-12 16:37 ` Pete Heist [this message]
2017-02-12 16:41 ` Jonathan Morton
2017-02-12 17:15 ` Pete Heist
2017-02-14 10:02 ` Pete Heist
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ED7C46F3-CBB7-4D71-BFB8-025EDF4C23CD@gmail.com \
--to=peteheist@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@gmail.com \
--cc=dave.taht@gmail.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