From: Jonathan Morton <chromatix99@gmail.com>
To: Bruno George Moraes <brunogm0@gmail.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Curious case of local "Fiber"
Date: Mon, 12 Feb 2018 15:56:35 +0200 [thread overview]
Message-ID: <A93344E5-04B2-4584-B9E4-1B82CE46A836@gmail.com> (raw)
In-Reply-To: <CAJpr3FNAvxNV1ShvtuGJ-xWzX0+7q8xYQigxMhiG=HFqb9C7EQ@mail.gmail.com>
> On 22 Jan, 2018, at 10:07 pm, Bruno George Moraes <brunogm0@gmail.com> wrote:
>
> My NIC is configured to only 1/1 buffers, then MTU 1492 (increased of default 1480), PPoE login with Windows 10 using CUBIC.
I didn't know Windows supported CUBIC. The default AFAIK is Compound TCP, if it isn't NewReno.
In any case, it looks like the bottleneck isn't at your NIC (so your settings don't matter), but at the router terminating the fibre for the whole building. That's the best place to mitigate the bloat, since it would work for the whole building's uplinks.
- Jonathan Morton
next prev parent reply other threads:[~2018-02-12 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 20:07 Bruno George Moraes
2018-02-12 13:56 ` Jonathan Morton [this message]
2018-02-12 14:01 ` Neal Cardwell
2018-02-12 14:34 ` Jim Gettys
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=A93344E5-04B2-4584-B9E4-1B82CE46A836@gmail.com \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=brunogm0@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