Lines Matching full:counters

22  * FS Summary Counters
28  * Then we compare what we computed against the in-core counters.
30  * However, the reality is that summary counters are a tricky beast to check.
41  * structures as quickly as it can.  We snapshot the percpu counters before and
48  * values, the percpu counters should be fairly close to each other.  However,
55  * contents and trust that the incore counters match the ondisk counters.  (The
57  * summary counters after checking all AG headers).  Do this from the setup
126 	/* We must get the incore counters set up before we can proceed. */  in xchk_setup_fscounters()
133 	 * likelihood of background perturbations to the counters throwing off  in xchk_setup_fscounters()
171  * Calculate what the global in-core counters ought to be from the incore
172  * per-AG structure.  Callers can compare this to the actual in-core counters
173  * to estimate by how much both in-core and on-disk counters need to be
219 		 * Per-AG reservations are taken out of the incore counters,  in xchk_fscount_aggregate_agcounts()
233 	 * counters, so leave that out of the computation.  in xchk_fscount_aggregate_agcounts()
238 	 * Delayed allocation reservations are taken out of the incore counters  in xchk_fscount_aggregate_agcounts()
257 	 * counters while we were calculating things.  We'll try a few times  in xchk_fscount_aggregate_agcounts()
329 /* Check the superblock counters. */
339 	/* Snapshot the percpu counters. */  in xchk_fscounters()
358 	 * something's probably wrong with the counters.  in xchk_fscounters()
363 	/* Walk the incore AG headers to calculate the expected counters. */  in xchk_fscounters()
370 	/* Compare the in-core counters with whatever we counted. */  in xchk_fscounters()