From: Jonathan Morton <chromatix99@gmail.com>
To: Kathleen Nichols <nichols@pollere.com>
Cc: codel@lists.bufferbloat.net
Subject: Re: [Codel] self tuning codel
Date: Thu, 19 Jul 2018 22:16:43 +0300 [thread overview]
Message-ID: <521F7AA2-5FE5-401F-964B-61F34C86A8FF@gmail.com> (raw)
In-Reply-To: <42959aa5-a266-bd75-a49b-38a726695f11@pollere.com>
> On 19 Jul, 2018, at 10:04 pm, Kathleen Nichols <nichols@pollere.com> wrote:
>
>> Thus, we let a specific AQM router serve
>> as a centralized DR in the system. All routers send packet
>> dropping probability updates to DR. DR then updates its list
>> of packet dropping probabilities and sends it to all routers
>
> Does this seem possible to anyone? There's an inherent assumption here
> that "dropping probabilities" are constant over a period of time that is
> long compared to the time to do the above. In what I've seen of traffic
> and AQMs this seems unlikely but I'm certainly not as well-informed on
> this as some people.
Based on the above, the approach seems completely wrong-headed to me. AQM should not be centralised, but must act according to local conditions. Certainly such a system would be impossible to deploy in a heterogeneous environment like the Internet.
>> every AQM router
>> needs to know all the packet dropping probabilities at the
>> bottleneck links in order to compute the window sizes of the
>> flows from (5).
As a first approximation, you can assume that if you are the bottleneck, nobody else on the same path is, and therefore their drop probabilities are all zero. This assumes only that you're dealing with traffic that's responsive to congestion signals, as TCP is. Transient conditions may exist where the assumption isn't entirely correct, but these are *only* transient.
The situation for UDP may of course be different.
- Jonathan Morton
next prev parent reply other threads:[~2018-07-19 19:16 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 [this message]
2018-07-20 6:00 ` Andrew McGregor
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=521F7AA2-5FE5-401F-964B-61F34C86A8FF@gmail.com \
--to=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=nichols@pollere.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