Lines Matching full:implicit

54 each zone has an implicit lock on the structures it manages for all its
361     This stage requires the data_vio to get an implicit lock on the
363     hashtable. This implicit locking is handled by the zone divisions
379        The implicit logical zone lock is released while the allocation is
386        (step 11), and reacquires the implicit logical zone lock to add the
395        to traverse the tree again. The data_vio then releases the implicit
401     compression are not possible. This stage gets an implicit lock on a
406     it will proceed to search the next physical zone by taking the implicit
413     hashtable is also covered by the implicit physical zone lock. The
416     sub-component of the slab and are thus also covered by the implicit
436     tracked in step 2. This hashtable is covered by the implicit lock on
442     also covered by the implicit hash zone lock. The hash lock agent will
491        implicit hash zone lock and go to the packer (struct packer) where
493        data_vios. All compression operations require the implicit lock on
515        The data_vio obtains an implicit lock on the physical zone and
517        modified to be a shared lock. Then it releases the implicit physical
524        lock, it will reacquire the implicit hash zone lock and share its
531        new data. The agent then releases the implicit hash zone lock.
541     on the block map cache structures, covered by the implicit logical zone
546     mapping. Making this journal entry requires holding the implicit
554     holding a lock on the affected physical slab, covered by its implicit
564     acquires the implicit logical zone lock and updates the
568 13. If the data_vio has a hash lock, it acquires the implicit hash zone
571     The data_vio then acquires the implicit physical zone lock and releases
576     The data_vio then acquires the implicit logical zone lock and releases