From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net,
Alan Jenkins <alan.christopher.jenkins@gmail.com>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Codel] [Cake] openwrt build available with latest cake and fq_pie
Date: Sun, 14 Jun 2015 11:24:52 -0700 [thread overview]
Message-ID: <CAA93jw7h=8LvjyOPdXdm7=mLqvmnp1CXw5+XWc_-vFfEaDbY+g@mail.gmail.com> (raw)
In-Reply-To: <EA30878E-70D6-4F32-BC55-31A34193E751@gmail.com>
On Sun, Jun 14, 2015 at 11:07 AM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 14 Jun, 2015, at 20:38, Dave Taht <dave.taht@gmail.com> wrote:
>>
>>> Every time Codel triggers the dropping state, it will mark or drop at least one packet, and increment count by that number. With count decremented only by 1 on recovery, it will effectively remain constant *if*, by some miracle, the queue empties before the second signal was sent; it cannot decrease between episodes unless it resets or wraps.
>>
>> It aint a miracle, it is hopefully within an rtt.
>
> No, it is *at minimum* one RTT. It takes that long for the congestion signal to reach the receiver, be reflected back to the sender, the sender’s reaction to *begin to* appear at the queue. Then the queue *starts* to empty, if the signal is what’s required to make it do so.
Flows, btw, do end quite rapidly in the real world. What was it, 95%
of all web flows ended inside of IW10? Dropping a packet at the tail
end of an ending flow forces a retransmit. Far too much of our testing
and thinking is oriented to full rate flows.
That is what I meant by "hopefully". I would like to build a test that
consisted primarily of short flows, one that hopefully looked more
like normal traffic.
>> When resuming the drop phase of codel, it is almost *already* too late
>> to catch that burst incurring the latency.
>
> Yes, but that’s what FQ is for. And ELR, if we ever get that properly started.
>
>> Sometimes I think we need to do away with the count idea and measure
>> slopes of curves instead, and "harmonics”.
>
>
>> 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?
>
> Such things are theoretically possible, but require further thought to determine how best to do them.
>
> - Jonathan Morton
>
--
Dave Täht
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast
next prev parent reply other threads:[~2015-06-14 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAA93jw6R2o+M68rQq07Qm8xBkr1bSvkVriysGdACxRLvmjhsmg@mail.gmail.com>
[not found] ` <CANmMgnGY1qkm9PnfKmHMoB6OYzhD5Cr9WDPPjmG1Tenw=+4E-g@mail.gmail.com>
[not found] ` <CAA93jw4XzLhudtQ=1+L6csv66d_sNgF6VLg8iqMZmPJHyc5ryw@mail.gmail.com>
[not found] ` <0CFA8991-9F5E-4988-82ED-6CA0E4E08676@gmail.com>
2015-06-14 17:38 ` Dave Taht
2015-06-14 18:07 ` Jonathan Morton
2015-06-14 18:24 ` Dave Taht [this message]
2015-06-14 19:35 ` Jonathan Morton
2015-06-14 19:42 ` 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='CAA93jw7h=8LvjyOPdXdm7=mLqvmnp1CXw5+XWc_-vFfEaDbY+g@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=alan.christopher.jenkins@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--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