Searched refs:unlocking (Results 1 – 19 of 19) sorted by relevance
| /linux-4.1.27/Documentation/locking/ |
| D | mutex-design.txt | 49 the unlocking fastpath is equally tight:
94 - Recursive locking/unlocking is not permitted.
|
| D | ww-mutex-design.txt | 253 /* need to do that before unlocking, since only the current lock holder is
327 unlocking all mutexes.
329 before unlocking all mutexes.
|
| D | rt-mutex.txt | 41 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| D | rt-mutex-design.txt | 512 wait_lock, the unlocking code would spin on the new owner's pi_lock
575 The wait_lock of the mutex is taken since the slow path of unlocking the
718 The unlocking of a mutex also has a fast path for those architectures with
721 take the slow path when unlocking the mutex. If the mutex doesn't have any
729 mutex. This synchronizes the locking and unlocking of the mutex.
|
| /linux-4.1.27/Documentation/ |
| D | robust-futex-ABI.txt | 69 in the middle of a locking or unlocking operation.
114 Actual locking and unlocking, during normal operations, is handled
|
| D | futex-requeue-pi.txt | 20 rest to the natural wakeup inherent in unlocking the mutex
|
| D | memory-barriers.txt | 2475 issued prior to unlocking the critical section.
|
| /linux-4.1.27/fs/dlm/ |
| D | dlm_internal.h | 691 struct list_head unlocking; member
|
| D | user.c | 652 INIT_LIST_HEAD(&proc->unlocking); in device_open()
|
| D | lock.c | 6000 list_move(&lkb->lkb_ownqueue, &ua->proc->unlocking); in dlm_user_unlock()
6197 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
6237 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in purge_proc_locks()
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 55 lead to deadlock, unless we played games with unlocking the i_sem
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | mandatory-locking.txt | 35 update, before applying its own lock, updating the file and unlocking it again.
|
| D | porting | 38 typically between calling iget_locked() and unlocking the inode.
|
| D | Locking | 271 followed by unlocking it. Once set_page_writeback() has been run against the
|
| D | vfs.txt | 283 unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
684 The filesystem must take care of unlocking the page and releasing it
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 760 associated object before unlocking the cookie.
|
| /linux-4.1.27/Documentation/vm/ |
| D | unevictable-lru.txt | 443 zeros out the page_mapping of the old page before unlocking it, so m[un]lock
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 365 However, strategic actions such as ejection of the tray, or unlocking
|
| /linux-4.1.27/Documentation/scsi/ |
| D | ChangeLog.lpfc | 419 and kernel complained about unlocking lock which is not locked.
|