From: "Simon Iremonger (bufferbloat)" <bufferbloat@iremonger.me.uk>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Fwd: [Bug 1436945] -> What other options/bufferbloat-advice ... ?
Date: Thu, 7 Jun 2018 13:56:55 +0100 [thread overview]
Message-ID: <0d7a4e82-bf1f-b18e-6f60-20ff173b2e1b@iremonger.me.uk> (raw)
In-Reply-To: <CAM9iV=+3j4hTSWO18EX5WkBFXc2Pcezpc6haTCHxAnM711rSEQ@mail.gmail.com>
>> What about PLPMTU? Do you think they might tweak that too?
>> net.ipv4.tcp_mtu_probing=2
>> (despite name, applies to IPv6 too)
>
> Maybe, suggest it on their github. But I would maybe propose instead
> net.ipv4.tcp_mtu_probing=1.
OK now this needs to become *organized* now...
What about putting explanations of the above into the
bufferbloat-wiki?
https://github.com/tohojo/bufferbloat-net/
What are the risks?
What is the advantages?
Are there other flags worth changing?
Can somebody who knows more help with checking on state of BBR
congestion control?
Which of these changes, depend on particular Linux versions,which MUST
NOT be applied without a particular kernel version?
etc...
Can somebody help make pull-requests on archiving "old" areas
of the bufferbloat-wiki e.g. old-changes that aren't relevant
any more given linux 3.2+ and soforth....?
https://github.com/tohojo/bufferbloat-net/
--Simon
next prev parent reply other threads:[~2018-06-07 12:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <152717340941.28154.812883711295847116.malone@soybean.canonical.com>
2018-05-24 15:38 ` [Bloat] Fwd: [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking Jan Ceuleers
2018-06-04 11:28 ` Bless, Roland (TM)
2018-06-04 13:16 ` Jonas Mårtensson
2018-06-04 17:08 ` Dave Taht
2018-06-04 18:22 ` Jonas Mårtensson
2018-06-04 21:36 ` Jonathan Morton
2018-06-05 15:10 ` [Bloat] " Jonathan Foulkes
2018-06-05 17:24 ` Jonathan Morton
2018-06-05 18:34 ` Sebastian Moeller
2018-06-05 19:31 ` Jonathan Morton
2018-06-06 6:53 ` Sebastian Moeller
2018-06-06 13:04 ` Jonathan Morton
2018-06-12 6:39 ` Dave Taht
2018-06-12 6:47 ` Dave Taht
2018-08-11 19:17 ` Dave Taht
2018-08-13 22:29 ` [Bloat] ecn redux Dave Taht
2018-06-06 7:44 ` [Bloat] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking Bless, Roland (TM)
2018-06-06 8:15 ` Sebastian Moeller
2018-06-06 8:55 ` Mario Hock
2018-06-05 0:22 ` [Bloat] Fwd: " Michael Richardson
2018-06-05 6:21 ` Jonas Mårtensson
2018-06-06 4:14 ` Mikael Abrahamsson
2018-06-07 12:56 ` Simon Iremonger (bufferbloat) [this message]
2018-06-04 23:00 ` David Lang
2018-06-05 7:44 ` Mario Hock
2018-06-05 7:49 ` Jonathan Morton
2018-06-05 11:01 ` Mario Hock
2018-08-16 21:08 ` 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/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=0d7a4e82-bf1f-b18e-6f60-20ff173b2e1b@iremonger.me.uk \
--to=bufferbloat@iremonger.me.uk \
--cc=bloat@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