Searched refs:Locks (Results 1 – 18 of 18) sorted by relevance
83 Locks are taken before writing and released once all statistics have84 been written. Locks are always released in case of an error. You
198 The PPP generic layer has been designed to be SMP-safe. Locks are
41 File Locks
28 1.2 Allow Mixed Locks Again
93 Locks for a given domain are represented by regular inodes inside the
23 locks victim and calls the method. Locks are exclusive.
22 of the list. Locks are granted in strictly the order that they
680 * Locks: none707 * Locks: None held727 * Locks: None held748 * Locks: None held766 * Locks: None held784 * Locks: None held809 * Locks: none842 * Locks: none877 * Locks: none held935 * Locks: up to and including 2.6.36, struct Scsi_Host::host_lock[all …]
132 * Locks are not taken outside of nportdisc, hbadisc, els and most
5 Voting Locks, or "vlocks" provide a simple low-level mutual exclusion
35 2. DLM Locks for management
101 Two Main Types of Kernel Locks: Spinlocks and Mutexes121 Locks and Uniprocessor Kernels1064 Avoiding Locks: Read Copy Update
2361 pSMB->Locks[0].Pid = cpu_to_le16(netpid); in CIFSSMBLock()2363 pSMB->Locks[0].LengthLow = cpu_to_le32((u32)len); in CIFSSMBLock()2364 pSMB->Locks[0].LengthHigh = cpu_to_le32((u32)(len>>32)); in CIFSSMBLock()2365 pSMB->Locks[0].OffsetLow = cpu_to_le32((u32)offset); in CIFSSMBLock()2366 pSMB->Locks[0].OffsetHigh = cpu_to_le32((u32)(offset>>32)); in CIFSSMBLock()
1099 LOCKING_ANDX_RANGE Locks[1]; member
566 Locks the latch, causing the detachment procedure to abort without opening
2922 Chapter 3.3: Hardware Considerations for Locks and
2077 Locks and semaphores may not provide any guarantee of ordering on UP compiled2342 locks. Locks, however, are quite expensive, and so it may be preferable to2976 Chapter 3.3: Hardware Considerations for Locks and
967 Locks the door of the drive. `arg == 0` unlocks the door,
