der Mouse  <mouse@Rodents.Montreal.QC.CA> writes:
> I've seen this sort of behavior often enough myself, and it's not
> hardware-specific.  Try the following program as an example.

What you've arranged is for the process to be awakened at every clock
tick.

That means that it's always ready to be run when the load average
calculator runs and so, not surprisingly, gets counted as runnable and
part of the system load.


This, and related issues, are known issues with the standard load
average calculation.  There've even been papers published on (quite)
similar topics...




cgd
-- 
Chris Demetriou - cgd@netbsd.org - http://www.netbsd.org/People/Pages/cgd.html
Disclaimer: Not speaking for NetBSD, just expressing my own opinion.