Subject: Re: cp_time[] - current "long", should be "u_int64_t"?
To: Simon Burge <simonb@netbsd.org>
From: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
List: tech-kern
Date: 05/28/2000 20:56:55
> + On a mostly idle 256HZ 32-bit machine (eg pmax), the CP_IDLE
> counter will overflow in approx 100 days.
> + In a compat32 situation on a 64 bit kernel the results of a
> userland program reading cp_time will be bogus.
>
> Any reasons not to do this?
Presumably you'll move the cp_time sysctl to a new mib slot when you
do this?
- Bill