From owner-freebsd-hackers Mon Feb 4 13:34:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from host213-123-128-100.in-addr.btopenworld.com (host213-123-128-100.in-addr.btopenworld.com [213.123.128.100]) by hub.freebsd.org (Postfix) with ESMTP id CCCBB37B426 for ; Mon, 4 Feb 2002 13:34:50 -0800 (PST) Received: by host213-123-128-100.in-addr.btopenworld.com (Postfix, from userid 1001) id 2CCCA72; Mon, 4 Feb 2002 21:34:50 +0000 (GMT) Date: Mon, 4 Feb 2002 21:34:50 +0000 From: Dominic Marks To: John Polstra Cc: hackers@freebsd.org Subject: Re: A question about timecounters Message-ID: <20020204213450.E923@gallium.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jdp@polstra.com on Mon, Feb 04, 2002 at 01:21:25PM -0800 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 On Mon, Feb 04, 2002 at 01:21:25PM -0800, John Polstra wrote: > 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. I see them everywhere with -CURRENT, but not at all with -STABLE. This is with two seperate machines. Perhaps that may add clues. > 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 -- Dominic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message