Lines Matching full:we

23  * We are limited in number of subclasses by MAX_LOCKDEP_SUBCLASSES, which at
24  * the time of this patch is 8, which is how many we use.  Keep this in mind if
31 	 * When we COW a block we are holding the lock on the original block,
33 	 * when we lock the newly allocated COW'd block.  Handle this by having
39 	 * Oftentimes we need to lock adjacent nodes on the same level while
40 	 * still holding the lock on the original node we searched to, such as
43 	 * Because of this we need to indicate to lockdep that this is
51 	 * When splitting we will be holding a lock on the left/right node when
52 	 * we need to cow that node, thus we need a new set of subclasses for
59 	 * When splitting we may push nodes to the left or right, but still use
61 	 * blocks.  Thus when we go to allocate a new split block we've already
63 	 * handle this case where we need to allocate a new split block.
68 	 * When promoting a new block to a root we need to have a special
69 	 * subclass so we don't confuse lockdep, as it will appear that we are
71 	 * has this problem as it appears we're locking the same block again
72 	 * when we make a snapshot of an existing root.
77 	 * We are limited to MAX_LOCKDEP_SUBCLASSES number of subclasses, so
79 	 * the limit.  As of this writing we're limited to 8, and we're
132  * Used to account for the fact that when doing io_uring encoded I/O, we can