On Thu, Sep 06, 2012 at 11:21:16AM -0700, David O'Brien wrote: > On Thu, Sep 06, 2012 at 09:39:24AM -0600, Ian Lepore wrote: > > On Wed, 2012-09-05 at 13:40 -0700, David O'Brien wrote:
> > Of those oids you listed above, the vm and vfs generate a lot of text > > but it's mostly the vm.stats part that changes. The kern.geom output is > > pretty static on a given system, and oddly it takes a long time to > > generate compared to other oids. The cp_time is already included in > > cp_times. The dev.cpu is intel-specific. > I'm not seeing that 'cp_time's specific values are in 'cp_times'. > I have not looked at how easy it is to derive 'cp_time' given > 'cp_times' output. That's trivial. The 'cp_time' output is the sum of the 'cp_times' output for all CPU cores. The 'cp_times' output has five numbers for each core. For example, in the '-' lines below, 568 + 36 = 604. > @@ -1,2 +1,2 @@ > -kern.cp_times: 4 0 568 3 548 22 0 36 42 397 > -kern.cp_time: 26 0 604 45 945 > +kern.cp_times: 102 0 636 6 8801479 104 0 126 52 8801316 > +kern.cp_time: 206 0 762 58 17602795 -- Jilles Tjoelker _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-rc To unsubscribe, send any mail to "[email protected]"
