Home
last modified time | relevance | path

Searched refs:woken (Results 1 – 25 of 55) sorted by relevance

123

/linux-6.1.9/Documentation/filesystems/nfs/
Dknfsd-stats.rst78 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-6.1.9/lib/
Dklist.c177 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-6.1.9/Documentation/admin-guide/pm/
Dsuspend-flows.rst104 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
Dsleep-states.rst38 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-6.1.9/Documentation/ABI/testing/
Dsysfs-class-power-surface8 necessary woken.
Dsysfs-class-remoteproc28 must be woken to receive messages.
Dsysfs-devices-platform-ACPI-TAD69 Bit(1): The timer has woken up the system from a sleep state
/linux-6.1.9/kernel/futex/
Dwaitwake.c399 static int futex_wait_multiple_setup(struct futex_vector *vs, int count, int *woken) in futex_wait_multiple_setup() argument
461 *woken = unqueue_multiple(vs, i); in futex_wait_multiple_setup()
462 if (*woken >= 0) in futex_wait_multiple_setup()
/linux-6.1.9/drivers/pci/hotplug/
DTODO11 * 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-6.1.9/kernel/locking/
Drwsem.c419 long oldcount, woken = 0, adjustment = 0; in rwsem_mark_wake() local
517 woken++; in rwsem_mark_wake()
523 if (unlikely(woken >= MAX_READERS_WAKEUP)) in rwsem_mark_wake()
527 adjustment = woken * RWSEM_READER_BIAS - adjustment; in rwsem_mark_wake()
528 lockevent_cond_inc(rwsem_wake_reader, woken); in rwsem_mark_wake()
539 } else if (woken) { in rwsem_mark_wake()
/linux-6.1.9/Documentation/locking/
Dfutex-requeue-pi.rst117 woken. futex_requeue() then proceeds to requeue the remaining
122 waiter is woken to finish the acquisition of the lock.
Drt-mutex.rst77 that has no owner and has been woken up to grab the lock.
Dmutex-design.rst66 the task is added to the wait-queue and sleeps until woken up by the
Drt-mutex-design.rst504 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-6.1.9/fs/ocfs2/dlm/
Ddlmmaster.c264 atomic_set(&mle->woken, 0); in dlm_init_mle()
1103 atomic_set(&mle->woken, 0); in dlm_wait_for_lock_mastery()
1105 (atomic_read(&mle->woken) == 1), in dlm_wait_for_lock_mastery()
1923 atomic_set(&mle->woken, 1); in dlm_assert_master_handler()
2682 (atomic_read(&mle->woken) == 1), in dlm_migrate_lockres()
2686 if (atomic_read(&mle->woken) == 1 || in dlm_migrate_lockres()
3221 atomic_set(&tmp->woken, 1); in dlm_add_migration_mle()
3292 atomic_set(&mle->woken, 1); in dlm_clean_migration_mle()
3317 atomic_set(&mle->woken, 1); in dlm_clean_block_mle()
3554 atomic_set(&mle->woken, 1); in dlm_force_free_mles()
/linux-6.1.9/net/smc/
Dsmc.h145 bool woken; member
/linux-6.1.9/Documentation/userspace-api/
Dfutex2.rst59 - Some futex at the list was woken, returning the index of some waked futex.
/linux-6.1.9/Documentation/scsi/
DChangeLog.ips111 - Make sure passthru commands get woken up if we run out of
/linux-6.1.9/Documentation/virt/kvm/x86/
Dhypercalls.rst99 specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0)
/linux-6.1.9/Documentation/mm/
Dbalance.rst66 problems: first, kswapd is woken up as in 2.2 on low memory conditions
/linux-6.1.9/Documentation/filesystems/
Dfuse.rst335 | [wake up fc->waitq] | [woken up]
352 | [woken up] | [wake up req->waitq]
/linux-6.1.9/Documentation/accounting/
Dpsi.rst70 Users can register triggers and use poll() to be woken up when resource
/linux-6.1.9/drivers/staging/greybus/Documentation/
Dsysfs-bus-greybus208 process watching the file will be woken up, and the new
/linux-6.1.9/Documentation/core-api/
Dcircular-buffers.rst180 CPU that the revised head index must be written before the consumer is woken.
/linux-6.1.9/Documentation/power/
Dcharger-manager.rst106 if the system was woken up by Charger Manager and the polling

123