hz(9) [netbsd man page]

HZ(9)							   BSD Kernel Developer's Manual						     HZ(9)

NAME

     hz, tick, tickadj, stathz, profhz -- system time model

SYNOPSIS

     #include <sys/kernel.h>

     extern int hz;
     extern int tick;
     extern int tickadj;
     extern int stathz;
     extern int profhz;

DESCRIPTION

     The essential clock handling routines in NetBSD are written to operate with two timers that run independently of each other.  The main clock,
     running hz times per second, is used to keep track of real time.

     In another words, hz specifies the number of times the hardclock(9) timer ticks per second.  Normally hardclock(9) increments time by tick
     each time it is called.  If the system clock has drifted, adjtime(2) may be used to skew this increment based on the rate of tickadj.

     The second timer is used to gather timing statistics.  It also handles kernel and user profiling.	If the second timer is programmable, it is
     randomized to avoid aliasing between the two clocks.  The mean frequency of the second timer is stathz.  If a separate clock is not avail-
     able, stathz is set to hz.

     If profiling is enabled, the clock normally used to drive stathz may be run at a higher rate profhz, which is required to be a multiple of
     stathz.  This will give higher resolution profiling information.

     These system variables are also available as struct clockinfo from sysctl(3) and kern.clockrate from sysctl(8).  The hz is hardware-depen-
     dent; it can be overridden (if the machine dependent code supports this) by defining HZ in the kernel configuration file (see options(4)).
     Only override the default value if you really know what you are doing.

SEE ALSO

     adjtime(2), callout(9), hardclock(9), microtime(9), time_second(9)

BSD
								  March 25, 2010							       BSD

CLOCKS(7)					       BSD Miscellaneous Information Manual						 CLOCKS(7)

NAME

     clocks -- various system timers

SYNOPSIS

     #include <time.h>

DESCRIPTION

     HZ is not part of the application interface in BSD.

     There are many different real and virtual (timekeeping) clocks with different frequencies:

     o	 The scheduling clock.	This is a real clock with frequency that happens to be 100.  It is not available to applications.

     o	 The statistics clock.	This is a real clock with frequency that happens to be 128.  It is not directly available to applications.

     o	 The clock reported by clock(3).  This is a virtual clock with a frequency that happens to be 128.  Its actual frequency is given by the
	 macro CLOCKS_PER_SEC.	Note that CLOCKS_PER_SEC may be floating point.  Do not use clock(3) in new programs under FreeBSD.  It is feeble
	 compared with getrusage(2).  It is provided for ANSI conformance.  It is implemented by calling getrusage(2) and throwing away informa-
	 tion and resolution.

     o	 The clock reported by times(3).  This is a virtual clock with a frequency that happens to be 128.  Its actual frequency is given by the
	 macro CLK_TCK (deprecated; do not use) and by sysconf(_SC_CLK_TCK) and by sysctl(3).  Note that its frequency may be different from
	 CLOCKS_PER_SEC.  Do not use times(3) in new programs under FreeBSD.  It is feeble compared with gettimeofday(2) together with
	 getrusage(2).	It is provided for POSIX conformance.  It is implemented by calling gettimeofday(2) and getrusage(2) and throwing away
	 information and resolution.

     o	 The profiling clock.  This is a real clock with frequency 1024.  It is used mainly by moncontrol(3), kgmon(8) and gprof(1).  Applications
	 should determine its actual frequency using sysctl(3) or by reading it from the header in the profiling data file.

     o	 The mc146818a clock.  This is a real clock with a nominal frequency of 32768.	It is divided down to give the statistic clock and the
	 profiling clock.  It is not available to applications.

     o	 The microseconds clock.  This is a virtual clock with frequency 1000000.  It is used for most timekeeping in BSD and is exported to
	 applications in getrusage(2), gettimeofday(2), select(2), getitimer(2), etc.  This is the clock that should normally be used by BSD
	 applications.

     o	 The i8254 clock.  This is a real clock/timer with a nominal frequency of 1193182.  It has three independent time counters to be used.	It
	 is divided down to give the scheduling clock.	It is not available to applications.

     o	 The TSC clock (64-bit register) on fifth-generation or later x86 systems.  This is a real clock with a frequency that is equivalent to
	 the number of cycles per second of the CPU(s).  Its frequency can be found using the machdep.tsc_freq sysctl, if it is available.  It is
	 used to interpolate between values of the scheduling clock.  It can be accessed using the PMIOTSTAMP request of perfmon(4).

     o	 The ACPI clock.  This is a real clock/timer with a nominal frequency of 3579545.  It is accessed via a 24 or 32 bit register.	Unlike the
	 TSC clock, it maintains a constant tick rate even when the CPU sleeps or its clock rate changes.  It is not available to applications.

     Summary: if HZ is not 1000000 then the application is probably using the wrong clock.

SEE ALSO

     gprof(1), clock_gettime(2), getitimer(2), getrusage(2), gettimeofday(2), select(2), clock(3), moncontrol(3), times(3)

AUTHORS

     This manual page was written by Jorg Wunsch after a description posted by Bruce Evans.

BSD
								 January 18, 2008							       BSD