Searched refs:Locks (Results 1 – 17 of 17) sorted by relevance
74 Locks are taken before writing and released once all statistics have75 been written. Locks are always released in case of an error. You
194 The PPP generic layer has been designed to be SMP-safe. Locks are
695 * Locks: none722 * Locks: None held742 * Locks: None held763 * Locks: None held781 * Locks: None held799 * Locks: None held824 * Locks: none857 * Locks: none892 * Locks: none held950 * 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
24 1.2 Allow Mixed Locks Again
88 Locks for a given domain are represented by regular inodes inside the
18 locks victim and calls the method. Locks are exclusive.
19 of the list. Locks are granted in strictly the order that they
38 File Locks
4 Voting Locks, or "vlocks" provide a simple low-level mutual exclusion
30 2. DLM Locks for management
107 Two Main Types of Kernel Locks: Spinlocks and Mutexes127 Locks and Uniprocessor Kernels1070 Avoiding Locks: Read Copy Update
2439 pSMB->Locks[0].Pid = cpu_to_le16(netpid); in CIFSSMBLock()2441 pSMB->Locks[0].LengthLow = cpu_to_le32((u32)len); in CIFSSMBLock()2442 pSMB->Locks[0].LengthHigh = cpu_to_le32((u32)(len>>32)); in CIFSSMBLock()2443 pSMB->Locks[0].OffsetLow = cpu_to_le32((u32)offset); in CIFSSMBLock()2444 pSMB->Locks[0].OffsetHigh = cpu_to_le32((u32)(offset>>32)); in CIFSSMBLock()
1132 LOCKING_ANDX_RANGE Locks[1]; member
3097 Chapter 3.3: Hardware Considerations for Locks and
2080 Locks and semaphores may not provide any guarantee of ordering on UP compiled2414 locks. Locks, however, are quite expensive, and so it may be preferable to3153 Chapter 3.3: Hardware Considerations for Locks and
946 \item[CDROM_LOCKDOOR] Locks the door of the drive. $arg == \rm0$
