From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net,
Alan Jenkins <alan.christopher.jenkins@gmail.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] openwrt build available with latest cake and fq_pie
Date: Sun, 14 Jun 2015 19:27:23 +0200 [thread overview]
Message-ID: <87a8w2qjyc.fsf@toke.dk> (raw)
In-Reply-To: <0CFA8991-9F5E-4988-82ED-6CA0E4E08676@gmail.com> (Jonathan Morton's message of "Sun, 14 Jun 2015 20:19:15 +0300")
Jonathan Morton <chromatix99@gmail.com> writes:
> *That* is why I put in count/2. A multiplicative decrease allows count
> to stabilise at some value which adequately controls the queue, rather
> than continuously increasing past it. For the typical cake case where
> there is one flow per Codel instance and the RTT is of Internet scale,
> this should work at least as well as an additive decrease; in
> particular, the behaviour is identical where count ended at 2, 3 or 4
> (it can’t end at 1).
Is there any reason why the decrease couldn't be some sort of decay?
I.e. a function of how long ago the drop state was exited?
-Toke
next prev parent reply other threads:[~2015-06-14 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 22:58 [Cerowrt-devel] " Dave Taht
2015-06-14 15:53 ` [Cerowrt-devel] [Cake] " Alan Jenkins
2015-06-14 16:09 ` Dave Taht
2015-06-14 17:19 ` Jonathan Morton
2015-06-14 17:27 ` Toke Høiland-Jørgensen [this message]
2015-06-14 17:38 ` Dave Taht
2015-06-14 18:07 ` Jonathan Morton
2015-06-14 18:24 ` Dave Taht
2015-06-14 19:35 ` Jonathan Morton
2015-06-14 19:42 ` Dave Taht
2015-06-14 19:32 ` Alan Jenkins
2015-06-14 19:47 ` Sebastian Moeller
2015-06-14 20:43 ` Alan Jenkins
2015-06-14 20:54 ` 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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8w2qjyc.fsf@toke.dk \
--to=toke@toke.dk \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@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