From owner-freebsd-hackers@freebsd.org  Fri Mar 16 16:12:05 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9C29F5A840
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Fri, 16 Mar 2018 16:12:05 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org
 [52.58.109.202])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 44F3A86ECC
 for <freebsd-hackers@freebsd.org>; Fri, 16 Mar 2018 16:12:04 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: c08f8e02-2934-11e8-91c6-33ffc249f3e8
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 67.177.211.60
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [67.177.211.60])
 by outbound1.eu.mailhop.org (Halon) with ESMTPSA
 id c08f8e02-2934-11e8-91c6-33ffc249f3e8;
 Fri, 16 Mar 2018 16:11:59 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w2GGBrB7029016;
 Fri, 16 Mar 2018 10:11:53 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1521216713.99081.55.camel@freebsd.org>
Subject: Re: option TCP_RFC7413 is not in GENERIC
From: Ian Lepore <ian@freebsd.org>
To: Patrick Kelsey <pkelsey@freebsd.org>, freebsd-hackers@freebsd.org
Date: Fri, 16 Mar 2018 10:11:53 -0600
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>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Mar 2018 16:12:05 -0000

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