From: Jonathan Morton <chromatix99@gmail.com>
To: "dpreed@deepplum.com" <dpreed@deepplum.com>
Cc: Dave Taht <dave.taht@gmail.com>,
cerowrt-devel@lists.bufferbloat.net,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] Invisibility of bufferbloat and its remedies
Date: Tue, 19 Jun 2018 02:17:46 +0300 [thread overview]
Message-ID: <8546545A-B1C8-47D8-A822-46C77A2DD5C8@gmail.com> (raw)
In-Reply-To: <1529361825.80979395@apps.rackspace.com>
> On 19 Jun, 2018, at 1:43 am, dpreed@deepplum.com wrote:
>
> So, no, the Network Neutrality people are NOT the problem with Bufferbloat.
No, but I think it's fair to point towards corporate greed and political ignorance as common causes of both problems.
- Jonathan Morton
next prev parent reply other threads:[~2018-06-18 23:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 16:26 [Cerowrt-devel] " dpreed
2018-06-18 19:07 ` Dave Taht
2018-06-18 22:43 ` dpreed
2018-06-18 23:17 ` Jonathan Morton [this message]
2018-06-19 2:21 ` [Cerowrt-devel] [Bloat] " dpreed
2018-06-19 1:46 ` [Cerowrt-devel] " Dave Taht
2018-06-19 19:33 ` Dave Taht
2018-06-19 19:45 ` dpreed
2018-06-19 20:34 ` valdis.kletnieks
2018-06-19 23:32 ` Sebastian Moeller
2018-06-20 6:56 ` [Cerowrt-devel] (no subject) Sebastian Moeller
2018-06-19 23:41 ` [Cerowrt-devel] Invisibility of bufferbloat and its remedies Jonathan Morton
2018-06-19 23:47 ` [Cerowrt-devel] [Bloat] " Sebastian Moeller
2018-06-20 7:12 ` Kevin Darbyshire-Bryant
2018-06-20 8:07 ` Sebastian Moeller
2018-06-20 9:15 ` Kevin Darbyshire-Bryant
2018-06-20 9:34 ` Sebastian Moeller
2018-06-18 20:59 ` [Cerowrt-devel] " Michael Richardson
2018-06-18 21:14 ` 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/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=8546545A-B1C8-47D8-A822-46C77A2DD5C8@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=dpreed@deepplum.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