Date: Fri, 24 Apr 2020 10:23:41 -0400 From: Mark Johnston <markj@freebsd.org> To: Tom Jones <thj@freebsd.org> Cc: freebsd-current@freebsd.org, freebsd-transport@freebsd.org Subject: Re: How to enable tcp bbr in FreeBSD??? Message-ID: <20200424142341.GB17086@raichu> In-Reply-To: <20200424141508.GB78595@tom-desk.erg.abdn.ac.uk> References: <20200424141508.GB78595@tom-desk.erg.abdn.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 24, 2020 at 03:15:08PM +0100, Tom Jones wrote: > rrs@freebsd.org > Bcc: > Subject: Re: How to enable tcp bbr in FreeBSD??? > Reply-To: > In-Reply-To: <6042155a-297b-d85e-1d64-24d93da329a2@gmail.com> > > > ... snip ... > > > > Maybe it is not ready for prime time, i do not know why it is not in the > > default build. > > Maybe ask the committer. > > > > I have added rrs@ in cc and the freebsd-transport list. > > Does anyone know if there are plans to enable alternate TCP stacks in > generic? > > Is there a stability point we need to hit first? There are a couple of open bugs found by syzkaller (complete with reproducers) that appeared when I enabled the alternate TCP stacks: https://syzkaller.appspot.com/bug?id=986b4cecd84439df9794bda1a45d9cf0f50356fe https://syzkaller.appspot.com/bug?id=048f650e99696f881872a285cef0e3b9bd4f4e25 I'd expect these to be fixed before providing the alternate stacks in GENERIC.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200424142341.GB17086>