From owner-freebsd-current@freebsd.org  Fri Apr 24 13:18:42 2020
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.nyi.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4160A2B3C53
 for <freebsd-current@mailman.nyi.freebsd.org>;
 Fri, 24 Apr 2020 13:18:42 +0000 (UTC) (envelope-from pi@freebsd.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 497vrL0qQQz4KG0
 for <freebsd-current@freebsd.org>; Fri, 24 Apr 2020 13:18:42 +0000 (UTC)
 (envelope-from pi@freebsd.org)
Received: from pi by home.opsec.eu with local (Exim 4.92.3 (FreeBSD))
 (envelope-from <pi@freebsd.org>)
 id 1jRyE1-0004GQ-Ub; Fri, 24 Apr 2020 15:18:37 +0200
Date: Fri, 24 Apr 2020 15:18:37 +0200
From: Kurt Jaeger <pi@freebsd.org>
To: "Herbert J. Skuhra" <herbert@gojira.at>
Cc: freebsd-current@freebsd.org
Subject: Re: How to enable tcp bbr in FreeBSD???
Message-ID: <20200424131837.GK39563@home.opsec.eu>
References: <CA+PGaYDZZHFGCR8tHbJT4me2kUwEUMP0mqnGf_MH7a8Sp7_P0g@mail.gmail.com>
 <F7C9C7F0-ADE2-4D01-AF29-4B9BF76FFA0C@gid.co.uk>
 <20200424113135.GH39563@home.opsec.eu>
 <20200424115425.GA64056@mail.bsd4all.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200424115425.GA64056@mail.bsd4all.net>
X-Rspamd-Queue-Id: 497vrL0qQQz4KG0
X-Spamd-Bar: -
Authentication-Results: mx1.freebsd.org;
	none
X-Spamd-Result: default: False [-1.85 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_MEDIUM(-0.91)[-0.914,0];
 NEURAL_HAM_LONG(-0.94)[-0.941,0];
 ASN(0.00)[asn:12502, ipnet:2001:14f8::/32, country:DE]
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Apr 2020 13:18:42 -0000

Hi!

> > Thanks. Is BBR active automatically or is there a sysctl or
> > socket option to activate it ?
> 
> net.inet.tcp.cc.available: List available congestion control algorithms
> net.inet.tcp.cc.algorithm: Default congestion control algorithm

Hmm, 

On my FreeBSD 13.0-CURRENT amd64 r359631M system:

$ sysctl -a | grep net.inet.tcp.cc
[...]
net.inet.tcp.cc.available: newreno
net.inet.tcp.cc.algorithm: newreno

So it's more recent than the patch, but it does not offer anything
besides newreno ?

-- 
pi@opsec.eu            +49 171 3101372                    Now what ?