From: Jonathan Morton <chromatix99@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] kind of hope they try FQ out in satellite conditions
Date: Thu, 22 Mar 2018 13:43:59 +0200 [thread overview]
Message-ID: <3B4C55F4-709D-4801-91BA-8760E73C65F3@gmail.com> (raw)
In-Reply-To: <25344A64-38CC-4AFB-8432-ED760ECD6318@gmail.com>
> On 22 Mar, 2018, at 12:57 pm, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 22 Mar, 2018, at 1:19 am, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> https://blog.apnic.net/2018/03/19/striking-a-balance-between-bufferbloat-and-tcp-queue-oscillation/
>
> The article says it's the second of three parts. Perhaps they will introduce FQ in the third part.
...or not. He talks about GEO vs. MEO instead.
https://blog.apnic.net/2018/03/20/geo-vs-meo-which-satellite-solution-works-best/
Time to start commenting.
- Jonathan Morton
prev parent reply other threads:[~2018-03-22 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 23:19 Dave Taht
2018-03-22 10:57 ` Jonathan Morton
2018-03-22 11:43 ` Jonathan Morton [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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3B4C55F4-709D-4801-91BA-8760E73C65F3@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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