From owner-freebsd-current@FreeBSD.ORG  Sat Mar  3 21:15:05 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 50B8216A400;
	Sat,  3 Mar 2007 21:15:05 +0000 (UTC)
	(envelope-from gallatin@cs.duke.edu)
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by mx1.freebsd.org (Postfix) with ESMTP id 13A9113C47E;
	Sat,  3 Mar 2007 21:15:04 +0000 (UTC)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.14.0/8.14.0) with ESMTP id l23LF4oJ005549
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 3 Mar 2007 16:15:04 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.12.9p2/8.12.9/Submit) id l23LEutt052140; 
	Sat, 3 Mar 2007 16:14:56 -0500 (EST) (envelope-from gallatin)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17897.58704.84621.191067@grasshopper.cs.duke.edu>
Date: Sat, 3 Mar 2007 16:14:56 -0500 (EST)
To: Scott Long <scottl@samsco.org>
In-Reply-To: <45E9A236.1080005@samsco.org>
References: <17850.13146.266196.499166@grasshopper.cs.duke.edu>
	<20070303000125.GA9918@turion.vk2pj.dyndns.org>
	<45E99060.3030404@freebsd.org> <45E9A236.1080005@samsco.org>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Cc: Peter Jeremy <peterjeremy@optushome.com.au>, freebsd-current@freebsd.org,
	Andre Oppermann <andre@freebsd.org>
Subject: Re: excessive TCP duplicate acks?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2007 21:15:05 -0000


Scott Long writes:
 > 
 > Just for fun, I wonder what would happen if HZ was set back to 100. 
 > It's not a fix, but it might point to some misconfigured timers.

I'm away, and the machines are powered off, but I could swear I set
hz back to 100.  I can grep in the serial console logs and see:

   Timecounters tick every 10.000 msec

I assume it would be every 1.000 msec if hz was at its default
value of 1000.

Drew