Lines Matching full:operations

6 Locking scheme used for directory operations is based on two
18 For our purposes all operations fall in 6 classes:
74 operations on directory trees, but we obviously do not have the full
77 Trees grow as we do operations; memory pressure prunes them.  Normally
108 the lock is dropped.  So from the directory operations' point of view
120 using a local one as a cache, etc.  In all such cases the operations
122 directory operation on this filesystem might involve directory operations
125 on a filesystem could trigger directory operations only on higher-ranked
160 It's easy to verify that operations never take a lock with rank
170 Moreover, without loss of generality we can assume that all operations
187 only 3 possible operations: directory removal (locks parent, then
192 if all operations had been of the "lock parent, then child" sort
199 Since all operations are on the same filesystem, there can't be
236 That concludes the proof, since the set of operations with the
253 These operations are guaranteed to avoid loop creation.  Indeed,
280 also preserved by all operations (cross-directory rename on a tree that would