Lines Matching refs:are

17     are completed.
20 just the holders) associated with the glock. If there are any
22 of the list. Locks are granted in strictly the order that they
23 are queued, except for those marked LM_FLAG_PRIORITY which are
26 There are three lock states that users of the glock layer can request,
41 operations. The glocks are basically a lock plus some routines which deal
53 These rules are implemented using the various glock operations which
54 are defined for each type of glock. Not all types of glocks use
79 prevent a situation where locks are being bounced around the cluster
81 tends to show up most with shared mmaped files which are being written
84 some progress before the pages are unmapped.
126 There are two glocks per inode. One deals with access to the inode
136 The stats are divided into two sets: those relating to the
138 super block stats are done on a per cpu basis in order to
139 try and reduce the overhead of gathering them. They are also
140 further divided by glock type. All timings are in nanoseconds.
144 block timing statistics are used to provide default values for
147 The per-glock counters are initialised to zero when the
148 glock is created. The per-glock statistics are lost when
151 The statistics are divided into three pairs of mean and
152 variance, plus two counters. The mean/variance pairs are
158 Unlike the TCP/IP Illustrated case, the mean and variance are
159 not scaled, but are in units of integer nanoseconds.
176 There are two counters. The first is there primarily to show
183 So why gather these statistics? There are several reasons
207 as possible. There are always inaccuracies in any
223 The abbreviations used in the output as are follows: