Date: Tue, 5 Feb 2002 11:06:08 -0800 (PST) From: John Polstra <jdp@polstra.com> To: hackers@freebsd.org Cc: phk@critter.freebsd.dk Subject: Re: A question about timecounters Message-ID: <200202051906.g15J68E04216@vashon.polstra.com> In-Reply-To: <91801.1012935515@critter.freebsd.dk> References: <91801.1012935515@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <91801.1012935515@critter.freebsd.dk>, Poul-Henning Kamp <phk@critter.freebsd.dk> wrote: > In message <200202051851.g15IpbU04184@vashon.polstra.com>, John Polstra writes: > >Yes, I think you're onto something now. It's a 550 MHz. machine, so > >the TSC increments every 1.82 nsec. And 1.82 nsec * 2^32 is 7.81 > >seconds. :-) > > In that case I'm almost willing to put an AnchorSteam on microuptime() > being interrupted for more than good is in which case the splhigh() should > cure it. I'm testing that now. But for how long would microuptime have to be interrupted to make this happen? Surely not 7.81 seconds! On this same machine I have a curses application running which is updating the screen once a second. It never misses a beat, and userland is very responsive. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa 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?200202051906.g15J68E04216>