From owner-freebsd-hackers Mon Feb 4 13:21:29 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 19F5237B419 for ; Mon, 4 Feb 2002 13:21:26 -0800 (PST) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g14LLPo48309 for ; Mon, 4 Feb 2002 13:21:25 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 04 Feb 2002 13:21:25 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: hackers@freebsd.org Subject: A question about timecounters Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm trying to understand the timecounter code, and in particular the reason for the "microuptime went backwards" messages which I see on just about every machine I have, whether running -stable or -current. This problem is usually attributed to too much interrupt latency. My question is, how much latency is "too much"? Which interrupt has to be locked out for how long in order to see these messages? John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message