Searched refs:futexes (Results 1 – 15 of 15) sorted by relevance
| /linux/Documentation/locking/ |
| H A D | robust-futexes.rst | 2 A description of what robust futexes are
10 what are robust futexes? To answer that, we first need to understand
11 what futexes are: normal futexes are special types of locks that in the
28 method makes futexes very lightweight and scalable.
45 (and in most cases there is none, futexes being fast lightweight locks)
56 robust futexes attached to this area'. This approach requires 3 new
75 because the kernel has no knowledge about how many robust futexes there
82 robust futexes impractical for any type of generic Linux distribution.
86 New approach to robust futexes
97 the cost of robust futexes is just a simple current->robust_list != NULL
[all …]
|
| H A D | index.rst | 25 robust-futexes
|
| H A D | pi-futex.rst | 2 Lightweight PI-futexes
12 similar to normal futexes.
82 futexes.) Userspace uses atomic ops to lock/unlock these mutexes without
118 properties of futexes, and all four combinations are possible: futex,
|
| H A D | rt-mutex.rst | 5 RT-mutexes with priority inheritance are used to support PI-futexes,
8 about PI-futexes.]
|
| H A D | robust-futex-ABI.rst | 9 futexes, for kernel assist of cleanup of held locks on task exit.
11 The interesting data as to what futexes a thread is holding is kept on a
15 required for futexes is:
22 The existing normal futexes already provide a "Fast Userspace Locking"
|
| H A D | futex-requeue-pi.rst | 54 be able to requeue tasks to PI futexes. This support implies that
|
| /linux/kernel/futex/ |
| H A D | syscalls.c | 448 struct futex_vector futexes[2]; in SYSCALL_DEFINE4() local
458 ret = futex_parse_waitv(futexes, waiters, 2, futex_wake_mark, NULL); in SYSCALL_DEFINE4()
462 cmpval = futexes[0].w.val; in SYSCALL_DEFINE4()
464 return futex_requeue(u64_to_user_ptr(futexes[0].w.uaddr), futexes[0].w.flags, in SYSCALL_DEFINE4()
465 u64_to_user_ptr(futexes[1].w.uaddr), futexes[1].w.flags, in SYSCALL_DEFINE4()
|
| /linux/Documentation/userspace-api/ |
| H A D | futex2.rst | 23 Wait on an array of futexes, wake on any::
77 private futexes, it's necessary to specify ``FUTEX_PRIVATE_FLAG`` in the futex
82 and shared futexes.
|
| /linux/tools/testing/selftests/futex/functional/ |
| H A D | futex_waitv.c | 26 u_int32_t futexes[NR_FUTEXES] = {0}; variable
57 waitv[i].uaddr = (uintptr_t)&futexes[i]; in TEST()
|
| /linux/Documentation/translations/zh_CN/locking/ |
| H A D | index.rst | 35 * robust-futexes
|
| /linux/Documentation/trace/rv/ |
| H A D | monitor_rtapp.rst | 62 this case, only futexes (FUTEX_LOCK_PI, FUTEX_LOCK_PI2 or one of
63 FUTEX_WAIT_*) should be used. Applications usually do not use futexes
65 top of futexes. Be aware that the C library might not implement conditional
|
| /linux/Documentation/gpu/ |
| H A D | drm-vm-bind-async.rst | 39 user-fences, userspace-fences or gpu futexes and do not necessarily obey
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | nommu-mmap.rst | 177 support futexes (such as an I/O chardev mapping).
|
| /linux/Documentation/driver-api/ |
| H A D | dma-buf.rst | 250 * Userspace fences or gpu futexes, fine-grained locking within a command buffer
|
| /linux/lib/ |
| H A D | Kconfig.debug | 2076 bool "Fault-injection capability for futexes"
2080 Provide fault-injection capability for futexes.
|