From owner-freebsd-bugs Tue Aug 13 9:30:10 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32AE437B401 for ; Tue, 13 Aug 2002 09:30:05 -0700 (PDT) Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC2E743E75 for ; Tue, 13 Aug 2002 09:30:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.4/8.12.4) with ESMTP id g7DGU4JU028150 for ; Tue, 13 Aug 2002 09:30:04 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.4/8.12.4/Submit) id g7DGU494028149; Tue, 13 Aug 2002 09:30:04 -0700 (PDT) Date: Tue, 13 Aug 2002 09:30:04 -0700 (PDT) Message-Id: <200208131630.g7DGU494028149@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: John Polstra Subject: Re: kern/41552: TCP timers' sysctl's overflow Reply-To: John Polstra Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/41552; it has been noted by GNATS. From: John Polstra To: bug-followup@freebsd.org Cc: bde@zeta.org.au Subject: Re: kern/41552: TCP timers' sysctl's overflow Date: Tue, 13 Aug 2002 09:24:19 -0700 (PDT) In article <200208131220.g7DCK5eQ076224@freefall.freebsd.org>, Bruce Evans wrote: > On Tue, 13 Aug 2002, G.P. de Boer wrote: > > Now the question pops up if setting HZ -is- unusual. I can imagine that > > there are many admins around who turned on polling for extra > > performance/robustness and tuned option HZ because LINT says so. > > Garrett clarified that setting hz to more than 1000 breaks more than the > TCP timer sysctls. It violates an RFC. I don't think that's a valid argument. Our hz value is an implementation detail which shouldn't have anything to do with RFCs. The nugget of truth buried in what Garrett said is that increasing hz tickles a _bug_ in our TCP implementation, which in turn causes the RFC to be violated. (The bug is the direct use of hz rather than the use of a scaled version of it.) The proper solution is to fix that bug, not to restrict the value of hz artificially. In my opinion, 100 ticks per second is a ridiculously low value for hz on modern systems. Even a PII/400 can run at hz=10000 without significant overhead. (I.e., the overhead can hardly be measured.) There are plenty of reasonable applications that utterly rely on elevated hz values. Dummynet is just one example. Note, I don't think the fix referenced in this PR should be merged into the security branches anyway, since it is not security related. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message