Date: Mon, 4 Feb 2002 21:34:50 +0000 From: Dominic Marks <dominic_marks@btinternet.com> To: John Polstra <jdp@polstra.com> Cc: hackers@freebsd.org Subject: Re: A question about timecounters Message-ID: <20020204213450.E923@gallium.localdomain> In-Reply-To: <XFMail.20020204132125.jdp@polstra.com>; from jdp@polstra.com on Mon, Feb 04, 2002 at 01:21:25PM -0800 References: <XFMail.20020204132125.jdp@polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020204213450.E923>