From owner-cvs-src@FreeBSD.ORG Thu Oct 20 15:21:32 2005 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC57816A420; Thu, 20 Oct 2005 15:21:32 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB39843D62; Thu, 20 Oct 2005 15:21:31 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9KFI4Iq010425; Thu, 20 Oct 2005 09:18:04 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 20 Oct 2005 09:19:25 -0600 (MDT) Message-Id: <20051020.091925.109166235.imp@bsdimp.com> To: scottl@samsco.org From: "M. Warner Losh" In-Reply-To: <4357AAFE.2070002@samsco.org> References: <20051020145234.H99720@delplex.bde.org> <200510200958.09182.jhb@freebsd.org> <4357AAFE.2070002@samsco.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 20 Oct 2005 09:18:06 -0600 (MDT) Cc: src-committers@freebsd.org, jhb@freebsd.org, bde@zeta.org.au, cvs-src@freebsd.org, cvs-all@freebsd.org, davidxu@freebsd.org, gallatin@cs.duke.edu Subject: Re: cvs commit: src/sys/amd64/amd64 cpu_switch.S machdep.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2005 15:21:32 -0000 In message: <4357AAFE.2070002@samsco.org> Scott Long writes: : However, I'd like to revisit the HZ=1000 decision for 7-CURRENT. At Timing Solutions, we run with HZ=1000 to reduce the latency for interacting with serial devices (since we have highly synchronous protocols that are spoken over them). Other than that, we've seen no performance differences between HZ=100 and HZ=1000 in other areas of our systems. We have noted a small increase in overhead with 1000, but since we have plenty of CPU to burn, we burn a little to get better latencies... We'll likely tune the number based on our experience, so changing the default HZ won't impact us. Warner