Re: [perf-discuss] Calculating segmap cache hits and misses

2009-03-12 Thread johansen
> Well, 4270983830 = 0xFE920A96 -- curiously close to the 32-bit > wraparound at 0x, eh? It looks like its cousin's value has > already wrapped. These sure look like 32-bit unsigned counters! These counters are defined as KSTAT_DATA_ULONG, which means that they're only 32-bits on a 32-b

Re: [perf-discuss] Calculating segmap cache hits and misses

2009-03-10 Thread Bob Sneed, SMI PAE
Well, 4270983830 = 0xFE920A96 -- curiously close to the 32-bit wraparound at 0x, eh? It looks like its cousin's value has already wrapped. These sure look like 32-bit unsigned counters! You'll fare better to start by taking the *deltas* over an interval. If a delta over an interval if

Re: [perf-discuss] Calculating segmap cache hits and misses

2009-03-10 Thread johansen
> I'm monitoring some very busy NFS clients and would like to graph the > segmap cache hits and misses. I took a look inside the code of the > segmapstat script included in Mr. Gregg's CacheKit collection, and I'm > getting some negative misses values in the results. I'm not sure I understan

[perf-discuss] Calculating segmap cache hits and misses

2009-03-10 Thread Dale Ghent
... properly that is :) I'm monitoring some very busy NFS clients and would like to graph the segmap cache hits and misses. I took a look inside the code of the segmapstat script included in Mr. Gregg's CacheKit collection, and I'm getting some negative misses values in the results. The