From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "cake@lists.bufferbloat.net" <cake@lists.bufferbloat.net>
Subject: [Cake] Cubic issues?
Date: Tue, 29 Sep 2015 21:57:59 +0000 [thread overview]
Message-ID: <E5E96CE2-D805-4D67-9F89-F6786BE95203@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 267 bytes --]
This is interesting http://www.theregister.co.uk/2015/09/29/google_cubists_fix_congestion_control_for_faster_tcp/
--
Cheers,
Kevin@Darbyshire-Bryant.me.uk
M: +44 7947 355344 H: +44 1256 478597
Sent from my phone, apologies for brevity, spelling & top posting
[-- Attachment #1.2: Type: text/html, Size: 627 bytes --]
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3062 bytes --]
next reply other threads:[~2015-09-29 21:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 21:57 Kevin Darbyshire-Bryant [this message]
2015-09-30 18:14 ` Alan Jenkins
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=E5E96CE2-D805-4D67-9F89-F6786BE95203@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@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