From: Adrian Popescu <adriannnpopescu@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Cake3 - source code and some questions
Date: Thu, 16 Apr 2015 16:48:53 +0300 [thread overview]
Message-ID: <CAF3M4P11YH4R48davyAddQhKnK_G1+zQcvGq_T4-DmAJd0LsYA@mail.gmail.com> (raw)
In-Reply-To: <5BC1CA30-289D-42B4-95CD-3AE5D7B96F09@gmail.com>
I've discovered there are other problems in the Linux networking stack
which don't seem to be related to fq_codel, qdiscs, AQM and HTB.
There are latency inducing issues bugs in the Ethernet network drivers
of many network adapters, including e1000e, or in the kernel itself.
Some kernels are better. The newest ones have severe regressions in
this area.
I was under the impression there's a problem in codel or fq_codel that
lead to very frequent latency micro-spikes of between 1 and 3
milliseconds. It also seemed to produce bigger latency spikes under
moderate load. No amount of tuning and disabling of offloads helped
with this.
Imagine having 2 milliseconds of latency to your ISP and having your
router induce between 3 to 5 milliseconds of latency for every flow.
It's not particularly helpful for low latency paths on high bandwidth
links. Adding more latency in both directions to high latency paths is
even worse.
These problems are the reason behind starting this thread. I believed
these problems to be related to fq_codel or to the codel algorithm
itself.
My question about porting these improvements to codel and fq_codel was
strictly about the tighter recovery, better invsqrt and other codel
enhancements mentioned on the wiki page.
The solution to this unstable latency will necessitate migration to
another platform without Linux. I'm aware cake and fq_codel won't fix
this problem on Linux.
next prev parent reply other threads:[~2015-04-16 13:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 9:39 Adrian Popescu
2015-04-12 9:58 ` Jonathan Morton
2015-04-12 10:24 ` Jonathan Morton
2015-04-12 12:33 ` Adrian Popescu
2015-04-12 18:57 ` Jonathan Morton
2015-04-16 12:14 ` Adrian Popescu
2015-04-16 13:25 ` Jonathan Morton
2015-04-16 13:48 ` Adrian Popescu [this message]
2015-04-16 19:26 ` Dave Taht
2015-04-22 21:02 ` Adrian Popescu
2015-04-23 0:45 ` Stephen Hemminger
2015-04-23 9:01 ` Toke Høiland-Jørgensen
2015-04-23 10:56 ` Adrian Popescu
2015-04-23 11:01 ` Toke Høiland-Jørgensen
2015-04-23 11:05 ` Adrian Popescu
2015-04-23 11:09 ` Toke Høiland-Jørgensen
2015-04-23 11:13 ` Jonathan Morton
2015-04-16 13:49 ` Sebastian Moeller
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=CAF3M4P11YH4R48davyAddQhKnK_G1+zQcvGq_T4-DmAJd0LsYA@mail.gmail.com \
--to=adriannnpopescu@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=chromatix99@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