Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 04 Nov 2000 13:45:20 +0900
From:      "Daniel C. Sobral" <dcs@newsguy.com>
To:        Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc:        Joerg Micheel <joerg@cs.waikato.ac.nz>, Zhiui Zhang <zzhang@cs.binghamton.edu>, freebsd-hackers@FreeBSD.ORG
Subject:   Re: granularity of gettimeofday()
Message-ID:  <3A039460.15D4C593@newsguy.com>
References:  <2017.973277815@critter>

next in thread | previous in thread | raw e-mail | index | archive | help
Poul-Henning Kamp wrote:
> 
> But the two *really* interesting things about the FreeBSD code is:
> 
>         You can change your timecounter on the fly.  This allows
>         the machine to boot using maybe the TSC, then load the
>         bitcode on the xrpu board, initialize the hardware on the
>         xrpu and start to use that as the timecounter.
> 
>         If the hardware can be read atomically, no interrupt
>         locking is used.  This means on a multi-CPU system you
>         will not have block interrupts to figure out what time
>         it is, in fact all CPUs can find out what time it is
>         *at the same time*, without interferring with each other.
> 
> I belive those two features are unique to FreeBSD at this time.

We need to write benchmarks that place heavy emphasis on these features,
then. :-)

-- 
Daniel C. Sobral			(8-DCS)
dcs@newsguy.com
dcs@freebsd.org
capo@world.wide.bsdconspiracy.net

		He has been convicted of criminal possession of a clue with intent to
distribute.


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?3A039460.15D4C593>