Subject: Re: cp_time[] - current "long", should be "u_int64_t"?
To: None <sommerfeld@orchard.arlington.ma.us>
From: Simon Burge <simonb@netbsd.org>
List: tech-kern
Date: 05/29/2000 11:08:48
Bill Sommerfeld wrote:
> > + 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?
That's a good question. :-) I was sorta hoping maybe to re-use the
current mib number and put this under the "-current is sometimes broken"
category since the current sysctl is only two or three days old...
Simon.