From: Jonathan Morton <chromatix99@gmail.com>
To: vignesh kannan <vignesh2496@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] (no subject)
Date: Wed, 29 Mar 2017 21:18:45 +0300 [thread overview]
Message-ID: <7FC0B78B-71E1-4D5C-8A49-035015EE3B06@gmail.com> (raw)
In-Reply-To: <CAAYLTGWopH_YcN6nET3HMNqe7Gjz42AUMi8cmSftqoAF0Fk0Vg@mail.gmail.com>
> On 29 Mar, 2017, at 21:15, vignesh kannan <vignesh2496@gmail.com> wrote:
>
> Can you please explain what a hard time cutoff is? I haven't come across the term before.
I mean that there’s a sharp transition from one calculation to another at some multiple of the interval in the older implementations. It always felt unnatural to me.
By contrast, Cobalt’s behaviour on re-entering dropping state depends smoothly on the time spent in the non-dropping state.
- Jonathan Morton
next prev parent reply other threads:[~2017-03-29 18:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 18:15 vignesh kannan
2017-03-29 18:18 ` Jonathan Morton [this message]
2017-03-29 18:25 ` vignesh kannan
-- strict thread matches above, loose matches on Subject: below --
2017-12-07 13:34 Mark Captur
2017-12-08 11:55 ` Andy Furniss
2016-12-26 12:44 Y
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7FC0B78B-71E1-4D5C-8A49-035015EE3B06@gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=vignesh2496@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