Subject: Re: cp_time[] - current "long", should be "u_int64_t"?
To: Bill Sommerfeld <sommerfeld@orchard.arlington.ma.us>
From: Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de>
List: tech-kern
Date: 05/29/2000 04:31:06
On Sun, 28 May 2000, Bill Sommerfeld wrote:
> > > 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...
> 
> Oh, oops, didn't realize that.  It shouldn't be a problem to reuse the
> same slot..
> 
> As Jason points out, extensions for per-cpu cp_time[] information
> would be worthwhile.

I guess the same will apply for procfs, too?


 - Hubert

-- 
NetBSD - because Unix isn't just #include <linux.h>, i386, ELF, ...!