Date: Fri, 16 Mar 2018 10:11:53 -0600 From: Ian Lepore <ian@freebsd.org> To: Patrick Kelsey <pkelsey@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: option TCP_RFC7413 is not in GENERIC Message-ID: <1521216713.99081.55.camel@freebsd.org> In-Reply-To: <CAD44qMUR_bKOzaWLMatGT3xXWdovWm3Abv8zwu=NCVm6YjEkiQ@mail.gmail.com> References: <1521062028.2511351.1303413736.6960BF4F@webmail.messagingengine.com> <20180314233811.GA35025@mail.bsd4all.net> <CAD44qMUR_bKOzaWLMatGT3xXWdovWm3Abv8zwu=NCVm6YjEkiQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2018-03-16 at 16:04 +0000, Patrick Kelsey wrote: > The current thinking is that users who care > about such performance differences are dealing with extreme workloads that > already motivate them to compile their own kernels, or are working with > very resource-constrained platforms, so the way forward is to keep the > TCP_RFC7413 kernel option around and enable it by default for the > server-class platforms (armd64 and arm64). I have no idea what TCP_RFC7413 even is, but I know I was forced to add it to my kernel config when I installed the bind911 package during a recent upgrade. This is on a tiny NUC for which saturating even one of its gbe interfaces would count as "extreme workload". :) -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1521216713.99081.55.camel>