Home
last modified time | relevance | path

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

12

/Linux-v5.4/Documentation/filesystems/nfs/
Dknfsd-stats.txt76 threads-woken
77 Counts how many times an idle nfsd thread is woken to try to
87 i.e. was not woken to handle any incoming network packets for
107 one of three ways. An nfsd thread can be woken (threads-woken counts
114 packets-deferred = packets-arrived - ( sockets-enqueued + threads-woken )
/Linux-v5.4/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-v5.4/kernel/locking/
Drwsem.c406 long oldcount, woken = 0, adjustment = 0; in rwsem_mark_wake() local
506 woken++; in rwsem_mark_wake()
512 if (woken >= MAX_READERS_WAKEUP) in rwsem_mark_wake()
516 adjustment = woken * RWSEM_READER_BIAS - adjustment; in rwsem_mark_wake()
517 lockevent_cond_inc(rwsem_wake_reader, woken); in rwsem_mark_wake()
527 if (woken && (atomic_long_read(&sem->count) & RWSEM_FLAG_HANDOFF)) in rwsem_mark_wake()
/Linux-v5.4/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-v5.4/Documentation/ABI/testing/
Dsysfs-class-remoteproc28 must be woken to receive messages.
Dsysfs-devices-platform-ACPI-TAD66 Bit(1): The timer has woken up the system from a sleep state
/Linux-v5.4/Documentation/
Dfutex-requeue-pi.txt117 woken. futex_requeue() then proceeds to requeue the remaining
122 waiter is woken to finish the acquisition of the lock.
/Linux-v5.4/fs/ocfs2/dlm/
Ddlmmaster.c266 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()
2686 (atomic_read(&mle->woken) == 1), in dlm_migrate_lockres()
2690 if (atomic_read(&mle->woken) == 1 || in dlm_migrate_lockres()
3226 atomic_set(&tmp->woken, 1); in dlm_add_migration_mle()
3297 atomic_set(&mle->woken, 1); in dlm_clean_migration_mle()
3322 atomic_set(&mle->woken, 1); in dlm_clean_block_mle()
3559 atomic_set(&mle->woken, 1); in dlm_force_free_mles()
Ddlmcommon.h50 atomic_t woken; member
/Linux-v5.4/Documentation/admin-guide/pm/
Dsleep-states.rst38 The system is woken up from this state by in-band interrupts, so theoretically
213 If the system is successfully woken up from that state, discard
219 just woken up from hibernation and the currently running kernel
/Linux-v5.4/Documentation/locking/
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-v5.4/Documentation/scsi/
DChangeLog.ips111 - Make sure passthru commands get woken up if we run out of
/Linux-v5.4/Documentation/networking/
Dx25-iface.txt120 CONFIG_NET_HW_FLOWCONTROL. This allows the driver to be woken up
/Linux-v5.4/Documentation/virt/kvm/
Dhypercalls.txt87 specifying APIC ID (a1) of the vcpu to be woken up. An additional argument (a0)
/Linux-v5.4/Documentation/vm/
Dbalance.rst66 problems: first, kswapd is woken up as in 2.2 on low memory conditions
/Linux-v5.4/Documentation/filesystems/
Dfuse.txt333 | [wake up fc->waitq] | [woken up]
350 | [woken up] | [wake up req->waitq]
/Linux-v5.4/Documentation/accounting/
Dpsi.rst69 Users can register triggers and use poll() to be woken up when resource
/Linux-v5.4/drivers/staging/greybus/Documentation/
Dsysfs-bus-greybus208 process watching the file will be woken up, and the new
/Linux-v5.4/Documentation/core-api/
Dcircular-buffers.rst180 CPU that the revised head index must be written before the consumer is woken.
/Linux-v5.4/Documentation/power/
Dcharger-manager.rst106 if the system was woken up by Charger Manager and the polling
Dswsusp.rst287 resume(): devices are woken up so that we can write image to swap
311 resume(): devices are woken up so that system can continue
/Linux-v5.4/Documentation/livepatch/
Dlivepatch.rst138 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
/Linux-v5.4/drivers/gpu/drm/nouveau/nvkm/engine/gr/fuc/
Dgpc.fuc291 // Main program loop, very simple, sleeps until woken up by the interrupt

12