Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Cubic issues?
Date: Wed, 30 Sep 2015 19:14:02 +0100	[thread overview]
Message-ID: <CANmMgnE8KBTKfsXtPZ2ijA1hoWjACG53_m19Xd88uiThRO3X2w@mail.gmail.com> (raw)
In-Reply-To: <E5E96CE2-D805-4D67-9F89-F6786BE95203@darbyshire-bryant.me.uk>

On 29/09/2015, Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> This is interesting
> http://www.theregister.co.uk/2015/09/29/google_cubists_fix_congestion_control_for_faster_tcp/

heh, I would recommend reading their source because they seemed to
omit the point

http://bitsup.blogspot.co.uk/2015/09/thanks-google-tcp-team-for-open-source.html

[Patrick McManus] The problem can be roughly summarized as the
controller mistakenly characterizing the lack of congestion reports
*over a quiescent period*  as positive evidence that the network is
not congested

[thereg] the bug was simple: TCP CUBIC interprets a lack of congestion
reports as an opportunity to send data at a faster rate.

[thereg] That condition could, however, arise merely because the
system hasn't been getting any congestion reports.

i.e. someone choked on the word quiescent and forgot to re-word it,
leaving a tautology.

Alan

      reply	other threads:[~2015-09-30 18:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 21:57 Kevin Darbyshire-Bryant
2015-09-30 18:14 ` Alan Jenkins [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/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=CANmMgnE8KBTKfsXtPZ2ijA1hoWjACG53_m19Xd88uiThRO3X2w@mail.gmail.com \
    --to=alan.christopher.jenkins@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=kevin@darbyshire-bryant.me.uk \
    /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