From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tribble.enyc.org.uk (tribble.enyc.org.uk [IPv6:2001:8b0:c1:2::26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A85D23B29E for ; Thu, 7 Jun 2018 08:57:03 -0400 (EDT) Received: from complexity.enyc.org.uk (unknown [IPv6:2001:630:c2:ff00::1fb]) by tribble.enyc.org.uk (Postfix) with ESMTPS id CA9CC401A7 for ; Thu, 7 Jun 2018 13:56:57 +0100 (BST) Received: from [IPv6:::1] (localhost [IPv6:::1]) by complexity.enyc.org.uk (Postfix) with ESMTP id 6F02F1401DD for ; Thu, 7 Jun 2018 13:56:55 +0100 (BST) From: "Simon Iremonger (bufferbloat)" To: bloat@lists.bufferbloat.net References: <152717340941.28154.812883711295847116.malone@soybean.canonical.com> <4f67f9b3-05a1-8d15-0aee-dfe8ea730d7c@gmail.com> <73c25a21-0ace-b5ee-090e-d06fb3b8dc60@kit.edu> <21947.1528158134@localhost> Message-ID: <0d7a4e82-bf1f-b18e-6f60-20ff173b2e1b@iremonger.me.uk> Date: Thu, 7 Jun 2018 13:56:55 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [Bloat] Fwd: [Bug 1436945] -> What other options/bufferbloat-advice ... ? X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2018 12:57:03 -0000 >> 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