Searched full:sleeping (Results 1 – 25 of 58) sorted by relevance
123
| /Documentation/scheduler/ |
| D | sched-eevdf.rst | 24 There are ongoing discussions on how to manage lag, especially for sleeping
27 by sleeping briefly to reset their negative lag: when a task sleeps, it
29 lag to decay over VRT. Hence, long-sleeping tasks eventually have their lag
|
| D | sched-arch.rst | 63 sleeping idle functions.
|
| /Documentation/timers/ |
| D | timers-howto.rst | 63 SLEEPING FOR "A FEW" USECS ( < ~10us? ):
73 SLEEPING FOR ~USECS OR SMALL MSECS ( 10us - 20ms):
103 SLEEPING FOR LARGER MSECS ( 10ms+ )
114 FLEXIBLE SLEEPING (any delay, uninterruptible)
|
| /Documentation/accounting/ |
| D | cgroupstats.rst | 29 sleeping 1, blocked 0, running 1, stopped 0, uninterruptible 0
31 sleeping 155, blocked 0, running 1, stopped 0, uninterruptible 2
|
| /Documentation/locking/ |
| D | locktypes.rst | 15 - Sleeping locks
26 Sleeping locks
29 Sleeping locks can only be acquired in preemptible task context.
34 versions of these primitives. In short, don't acquire sleeping locks from
37 Sleeping lock types:
46 On PREEMPT_RT kernels, these lock types are converted to sleeping locks:
512 - Lock types of the same lock category (sleeping, CPU local, spinning)
516 - Sleeping lock types cannot nest inside CPU local and spinning lock types.
518 - CPU local and spinning lock types can nest inside sleeping lock types.
525 rwlock_t from spinning to sleeping and substitutes local_lock with a
[all …]
|
| D | mutex-design.rst | 15 or similar theoretical text books. Mutexes are sleeping locks which
57 for sleeping lock implementation. An important feature of the customized
71 task and busy-waiting for a few cycles instead of immediately sleeping,
104 Mutexes - and most other sleeping locks like rwsems - do not provide an
|
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 56 2) Waking a sleeping VCPU. Sleeping VCPUs are VCPU threads outside guest
61 sleeping, then there is nothing to do.
153 from VCPUs running in guest mode. That is, sleeping VCPUs do not need
154 to be awakened for these requests. Sleeping VCPUs will handle the
162 If, for example, the VCPU is sleeping, so no IPI is necessary, then
279 Sleeping VCPUs
|
| /Documentation/usb/ |
| D | dwc3.rst | 39 sleeping is handed over to the Thread. The event is saved in an
|
| /Documentation/devicetree/bindings/input/ |
| D | syna,rmi4.yaml | 69 If set the device will run at full power without sleeping. nosleep
71 nosleep (allow sleeping), and 2 will enable nosleep (disabling
|
| /Documentation/userspace-api/media/ |
| D | gen-errors.rst | 24 device is sleeping and ioctl is performed to query statistics. It
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 97 1. The first and most effective approach is stack checking of sleeping
108 a) Patching I/O-bound user tasks which are sleeping on an affected
163 are sleeping in (/proc/<pid>/stack may help here). Removal (rmmod) of patch
165 guaranteed there is no task sleeping in such module. It implies unbounded
|
| /Documentation/userspace-api/ |
| D | futex2.rst | 58 - A signal was sent to the sleeping task, returning ``-ERESTARTSYS``.
|
| /Documentation/infiniband/ |
| D | core_locking.rst | 10 Sleeping and interrupt context
|
| /Documentation/devicetree/bindings/firmware/ |
| D | qcom,scm.yaml | 93 protocol to handle sleeping SCM calls.
|
| /Documentation/mm/ |
| D | balance.rst | 75 and all process contexts are sleeping. For 2.3, kswapd does not really
|
| D | page_migration.rst | 127 to sleeping on the locked new page.
|
| D | multigen_lru.rst | 179 have been sleeping since the last iteration.
|
| /Documentation/input/ |
| D | input-programming.rst | 193 too. Being a wakeup source plays a role when the system is sleeping, not when
195 inhibiting, sleeping and being a wakeup source is driver-specific.
|
| /Documentation/virt/kvm/x86/ |
| D | hypercalls.rst | 98 same guest can wakeup the sleeping vcpu by issuing KVM_HC_KICK_CPU hypercall,
|
| /Documentation/admin-guide/laptops/ |
| D | sonypi.rst | 132 Fn-keys which put the laptop in sleeping state, or switch the
|
| /Documentation/trace/ |
| D | mmiotrace.rst | 65 The 'cat' process should stay running (sleeping) in the background.
|
| /Documentation/core-api/ |
| D | memory-allocation.rst | 108 non sleeping allocation with an expensive fallback so it can access
|
| /Documentation/driver-api/gpio/ |
| D | consumer.rst | 231 Also, using these calls for GPIOs that can't safely be accessed without sleeping
240 sleeping, which can't be done from inside IRQ handlers.
|
| /Documentation/networking/ |
| D | netdevices.rst | 293 all NAPI instances which will do a sleeping poll on the
|
| /Documentation/filesystems/xfs/ |
| D | xfs-delayed-logging-design.rst | 265 To take a new reservation without sleeping requires us to be able to take a
809 be able to reserve the space without sleeping. For a 8MB checkpoint, we need a
932 really needs to be a sleeping lock - if the CIL flush takes the lock, we do not
937 main reason for choosing a sleeping lock even though nothing in either the
|
123