Date: Sat, 23 Apr 2022 09:24:23 +0200 From: Gordon Bergling <gbe@freebsd.org> To: Michael Tuexen <michael.tuexen@lurchi.franken.de> Cc: net@freebsd.org Subject: Re: Enabling EXTRA_TCP_STACKS on stable/13 Message-ID: <YmOpp9qRT22yxmgL@lion.ttyv0.de> In-Reply-To: <9EC02E05-73AA-4F31-9A52-9BC5E159D9EE@lurchi.franken.de> References: <YmLP54Ft4J1ucO%2Bb@lion.ttyv0.de> <9EC02E05-73AA-4F31-9A52-9BC5E159D9EE@lurchi.franken.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--okIkbpuuCnh5lNZk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Michael, On Fri, Apr 22, 2022 at 08:36:42PM +0200, Michael Tuexen wrote: > > On 22. Apr 2022, at 17:55, Gordon Bergling <gbe@FreeBSD.org> wrote: > > I recently build some personal infrastructure and experimented a little > > bit with tcp_bbr(4) and tcp_rack. Doing is this in a cloud environment > > is a little bit priced since the kernel must be rebuild with the build > > options EXTRA_TCP_STACKS defined. > >=20 > > Would it be feasable to switch this option to on by default? > Wouldn't we also need > options TCPHTPS Thats true, I could provide a differential that would cover this aswell. > > I would think that the rack and bbr are stable enough for further > > adoption. > I would say we can do so for RACK in the master branch. Not sure about > BBR, since it implements BBRv1, which is known to be unfair in some > situations (this is not a property of the FreeBSD implementation, > but of the algorithm). I am not sure if this can be easly accomplished since I don't know the implementation of the build switch. I just would reverse the build switch so BBR and RACK would be available. > I'm not sure about stable/13, since a lot of changes haven't been > backported. You are right about this. We should MFC all changes since we ship to code already with a second RELEASE coming up. If we build both extra stacks on -CURRENT a MFC could be set with an MFC-window from=20 about 1-2 month. > We can discuss this at the next transport conference call. Are you > interested to join (scheduled for May 5th, 15:00 UTC)? I could try to attent the call, but I am not sure if I could make in time. --Gordon --okIkbpuuCnh5lNZk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYbWI0KY5X7yH/Fy4OQX2V8rP09wFAmJjqaVfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYx QjU4OEQwQTYzOTVGQkM4N0ZDNUNCODM5MDVGNjU3Q0FDRkQzREMACgkQOQX2V8rP 09xYoAf8CqJyQfKRSxVQt9NZVVBRkcBYnu8aY1S+ejjbSV6xg6inzXo8genzo3h1 BXRdUWl2NjvIrmpmips4SO2oy0QWi2BBBKpiwsBgrBwdz9l3s4hIQasUa4XHSbMv t7j1J9zwno/Ej3b/s1LTasD9OXBQY3j36YyLVvPY39ygedqd4KylRWOb5dBlQ/vH qTZJY+GfaCBHCR/hash6A82z7Wg9sdqatBikr6VBege6br3vdu6xkrVkfpxchIbV AwbauarhpA/r52SPnklzieQ/wGXAl1kdQ/XBsWd00KRem0TpkHDfwiWI0G/Su1/+ uaskr+L28PcYW81o82js3HkJydd53A== =emtk -----END PGP SIGNATURE----- --okIkbpuuCnh5lNZk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YmOpp9qRT22yxmgL>