From: Andrew McGregor <andrewmcgr@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] self tuning codel
Date: Fri, 20 Jul 2018 16:00:56 +1000 [thread overview]
Message-ID: <CAA_e5Z5bK2QHLmJ7S-S+dYYdTaBuUzh2Ge4Hwi-KNQ8rcdCnEw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4JvAiDvEa3zAxNb9wyqmNyPKqGqW2H7h-fWnSPOj-x5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
So, it has a core assumption: that a stable arrangement of links with small
persistent delays is something that both can and should exist.
It's kind of like a fluid model, in many ways.
Thing is, I don't think it's desirable that persistent delays exist
anywhere.
Now, autotuning codel is probably a good idea... but the implementation
should be local. If you're a bottleneck, you may as well behave as if
you're the only bottleneck, even if that isn't the case, because if you're
in a distributed bottleneck situation your actions will help anyway. A
global distributed solver like is proposed here could possibly work in a
private network, but I can't see that solution flying in precisely the
place you really need it: peering.
One way to do this locally would be to identify the impulse response of the
stochastic DE describing the aggregate running through the link using
something like https://arxiv.org/abs/1309.7857 and then tune to optimal
behaviour for the resulting DE, along the lines of
https://arxiv.org/abs/1510.08439.
On Thu, Jul 19, 2018 at 8:42 AM Dave Taht <dave.taht@gmail.com> wrote:
> there's so much math in this that I cannot make heads or tails of it.
>
>
> https://www.eee.hku.hk/~kcleung/papers/conferences/bufferbloat_multi-bottleneck:INFOCOM_2018/PID5170809.pdf
>
> --
>
> Dave Täht
> CEO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-669-226-2619
> _______________________________________________
> Codel mailing list
> Codel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel
>
[-- Attachment #2: Type: text/html, Size: 2446 bytes --]
prev parent reply other threads:[~2018-07-20 6:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 22:42 Dave Taht
2018-07-19 19:04 ` Kathleen Nichols
2018-07-19 19:16 ` Jonathan Morton
2018-07-20 6:00 ` Andrew McGregor [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/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=CAA_e5Z5bK2QHLmJ7S-S+dYYdTaBuUzh2Ge4Hwi-KNQ8rcdCnEw@mail.gmail.com \
--to=andrewmcgr@gmail.com \
--cc=codel@lists.bufferbloat.net \
--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