> > 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.

				- Bill