From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] more from cloudflare on their latency spike
Date: Sat, 9 Apr 2016 09:18:35 -0700 [thread overview]
Message-ID: <CAA93jw40-tbwSJWY5w9zqgNa-9Nd6U8edF7zXDASoU-7M7icow@mail.gmail.com> (raw)
a few months or weeks ago we'd discussed the prior event at cloudflare
that they had dissected so well. Dave Reed, in particular, had pointed
to bufferbloat as a potential cause of the problem they had
mis-diagnosed, (I was dubious) and they had continued to hack at it.
The final answer was quite fascinating.
https://blog.cloudflare.com/revenge-listening-sockets/?p=0
--
Dave Täht
Let's go make home routers and wifi faster! With better software!
https://www.gofundme.com/savewifi
reply other threads:[~2016-04-09 16:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw40-tbwSJWY5w9zqgNa-9Nd6U8edF7zXDASoU-7M7icow@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@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