From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] The next slice of cake
Date: Wed, 18 Mar 2015 14:20:52 -0700 [thread overview]
Message-ID: <CAA93jw7JVjvj9QYCLYT+UHOLDPSmdYB4uAp8wf+B=TL9pOrxrA@mail.gmail.com> (raw)
In-Reply-To: <491C7497-BE3E-452B-A797-C7FC1102E7ED@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]
On Wed, Mar 18, 2015 at 8:20 AM, Jonathan Morton <chromatix99@gmail.com>
wrote:
>
> > On 18 Mar, 2015, at 17:10, Kathleen Nichols <nichols@pollere.com> wrote:
> >
> > How are you relating target delay to bandwidth?
>
> Essentially, I use 5ms as a minimum, and increase it if necessary to
> accommodate a couple of MTU-sized packets at the shaping rate. This keeps
> things nicely under control at low bandwidths, and I find that cake remains
> useful and usable even at 64Kbps (without making even the usual adjustments
> to host or link configuration for such low speeds).
>
In the cake2 (or maybe it was the unpublished cake3) version, I had a
lighter weight version of the codel algorithm, that did not have a target
parameter at all. Instead it just took the interval parameter and shifted
it
right 4 (yielding a target of 6.xms from an interval of 100ms)
This saves on a memory access (and storage per queue!) , and I felt that
any differences in behavior would be unnoticeable. And they were. This is
also above the bound for cable-modem media access that greg white (rightly
or wrongly) believed existed. So I have no problem in eliminating "target"
entirely.
Cake (without bandwidth shaping engaged) uses more cpu than fq_codel did
and this was one of many optimizations I'd attempted (or successfully
added). Cake with shaping is a bit less cpu than sqm-scripts htb + fq_codel
+ filters.
It also looked like cake could be poured into gates, with a bit more
research, and testing.
> I can do this in cake because the shaping rate is known, whereas the pure
> codel and fq_codel qdiscs do not have reliable link-speed information.
As for this bit, we seemed to need to account for a MTU's worth of data at
the lower speeds, and I did not explore what fiddling with the interval and
auto-calc-ing the target did at these speeds, as yet.
> - Jonathan Morton
>
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
[-- Attachment #2: Type: text/html, Size: 3339 bytes --]
next prev parent reply other threads:[~2015-03-18 21:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:08 Jonathan Morton
2015-03-18 7:22 ` Sebastian Moeller
2015-03-18 8:41 ` Jonathan Morton
2015-03-18 10:39 ` Sebastian Moeller
2015-03-18 15:10 ` Kathleen Nichols
2015-03-18 15:20 ` Jonathan Morton
2015-03-18 21:20 ` Dave Taht [this message]
2015-03-21 16:09 ` Dave Taht
2015-03-21 23:55 ` Jonathan Morton
2015-03-22 9:39 ` Sebastian Moeller
2015-03-22 10:43 ` Jonathan Morton
2015-03-22 12:51 ` Sebastian Moeller
2015-03-22 15:29 ` Jonathan Morton
2015-03-30 17:28 ` Jonathan Morton
2015-03-30 18:23 ` Sebastian Moeller
2015-03-31 3:22 ` Jonathan Morton
2015-03-31 7:12 ` Sebastian Moeller
2015-03-31 12:47 ` Jonathan Morton
2015-03-30 19:28 ` Dave Taht
2015-04-02 4:48 ` Jonathan Morton
2015-04-02 5:17 ` Dave Taht
2015-04-02 5:19 ` Dave Taht
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='CAA93jw7JVjvj9QYCLYT+UHOLDPSmdYB4uAp8wf+B=TL9pOrxrA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
/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