| /Linux-v5.10/Documentation/filesystems/nfs/ |
| D | knfsd-stats.rst | 78 threads-woken
79 Counts how many times an idle nfsd thread is woken to try to
89 i.e. was not woken to handle any incoming network packets for
109 one of three ways. An nfsd thread can be woken (threads-woken counts
116 packets-deferred = packets-arrived - ( sockets-enqueued + threads-woken )
|
| /Linux-v5.10/lib/ |
| D | klist.c | 177 int woken; member
196 waiter->woken = 1; in klist_release()
244 waiter.woken = 0; in klist_remove()
253 if (waiter.woken) in klist_remove()
|
| /Linux-v5.10/Documentation/admin-guide/pm/ |
| D | suspend-flows.rst | 104 the tick do not occur until the CPU is woken up by another interrupt source.
108 forward until the first CPU that is woken up restarts the timekeeping.
112 From this point on, the CPUs can only be woken up by non-timer hardware
128 When one of the CPUs is woken up (by a non-timer hardware interrupt), it
134 If the interrupt that has woken up the CPU was armed for system wakeup,
153 transition are "thawed", which means that they are woken up from the
241 The platform is woken up by a signal from one of the designated system
|
| D | sleep-states.rst | 38 The system is woken up from this state by in-band interrupts, so theoretically
223 If the system is successfully woken up from that state, discard
231 just woken up from hibernation and the currently running kernel
|
| /Linux-v5.10/kernel/locking/ |
| D | rwsem.c | 405 long oldcount, woken = 0, adjustment = 0; in rwsem_mark_wake() local
505 woken++; in rwsem_mark_wake()
511 if (woken >= MAX_READERS_WAKEUP) in rwsem_mark_wake()
515 adjustment = woken * RWSEM_READER_BIAS - adjustment; in rwsem_mark_wake()
516 lockevent_cond_inc(rwsem_wake_reader, woken); in rwsem_mark_wake()
526 if (woken && (atomic_long_read(&sem->count) & RWSEM_FLAG_HANDOFF)) in rwsem_mark_wake()
|
| /Linux-v5.10/drivers/pci/hotplug/ |
| D | TODO | 11 * The driver spawns a kthread cpqhp_event_thread() which is woken by the
13 The kthread is also woken from the timer pushbutton_helper_thread(),
|
| /Linux-v5.10/Documentation/locking/ |
| D | futex-requeue-pi.rst | 117 woken. futex_requeue() then proceeds to requeue the remaining
122 waiter is woken to finish the acquisition of the lock.
|
| D | rt-mutex.rst | 77 that has no owner and has been woken up to grab the lock.
|
| D | mutex-design.rst | 66 the task is added to the wait-queue and sleeps until woken up by the
|
| D | rt-mutex-design.rst | 504 could get the lock, then it will go back to sleep and wait to be woken again.
508 a timeout (i.e. rt_mutex_timed_futex_lock()). When woken, it will try to
510 lock held, otherwise it will return with -EINTR if the task was woken
|
| /Linux-v5.10/fs/ocfs2/dlm/ |
| D | dlmmaster.c | 266 atomic_set(&mle->woken, 0); in dlm_init_mle()
1105 atomic_set(&mle->woken, 0); in dlm_wait_for_lock_mastery()
1107 (atomic_read(&mle->woken) == 1), in dlm_wait_for_lock_mastery()
1925 atomic_set(&mle->woken, 1); in dlm_assert_master_handler()
2684 (atomic_read(&mle->woken) == 1), in dlm_migrate_lockres()
2688 if (atomic_read(&mle->woken) == 1 || in dlm_migrate_lockres()
3223 atomic_set(&tmp->woken, 1); in dlm_add_migration_mle()
3294 atomic_set(&mle->woken, 1); in dlm_clean_migration_mle()
3319 atomic_set(&mle->woken, 1); in dlm_clean_block_mle()
3556 atomic_set(&mle->woken, 1); in dlm_force_free_mles()
|
| D | dlmcommon.h | 50 atomic_t woken; member
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-class-remoteproc | 28 must be woken to receive messages.
|
| D | sysfs-devices-platform-ACPI-TAD | 69 Bit(1): The timer has woken up the system from a sleep state
|
| /Linux-v5.10/Documentation/scsi/ |
| D | ChangeLog.ips | 111 - Make sure passthru commands get woken up if we run out of
|
| /Linux-v5.10/Documentation/networking/ |
| D | x25-iface.rst | 126 CONFIG_NET_HW_FLOWCONTROL. This allows the driver to be woken up
|
| /Linux-v5.10/Documentation/virt/kvm/ |
| D | hypercalls.rst | 99 specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0)
|
| /Linux-v5.10/Documentation/vm/ |
| D | balance.rst | 66 problems: first, kswapd is woken up as in 2.2 on low memory conditions
|
| /Linux-v5.10/Documentation/filesystems/ |
| D | fuse.rst | 316 | [wake up fc->waitq] | [woken up]
333 | [woken up] | [wake up req->waitq]
|
| /Linux-v5.10/Documentation/accounting/ |
| D | psi.rst | 71 Users can register triggers and use poll() to be woken up when resource
|
| /Linux-v5.10/drivers/staging/greybus/Documentation/ |
| D | sysfs-bus-greybus | 208 process watching the file will be woken up, and the new
|
| /Linux-v5.10/Documentation/core-api/ |
| D | circular-buffers.rst | 180 CPU that the revised head index must be written before the consumer is woken.
|
| /Linux-v5.10/Documentation/power/ |
| D | charger-manager.rst | 106 if the system was woken up by Charger Manager and the polling
|
| D | swsusp.rst | 289 resume(): devices are woken up so that we can write image to swap
313 resume(): devices are woken up so that system can continue
|
| /Linux-v5.10/Documentation/livepatch/ |
| D | livepatch.rst | 138 especially applies to kthreads. They may not be woken up and would need
164 interrupted or woken up, and forced to change their patched state. The fake
|
