Searched full:rt (Results 1 – 25 of 38) sorted by relevance
12
| /Documentation/locking/ |
| D | rt-mutex.rst | 2 RT-mutex subsystem with PI support
5 RT-mutexes with priority inheritance are used to support PI-futexes,
10 This technology was developed in the -rt tree and streamlined for
16 RT-mutexes extend the semantics of simple mutexes by the priority
19 A low priority owner of a rt-mutex inherits the priority of a higher
20 priority waiter until the rt-mutex is released. If the temporarily
21 boosted owner blocks on a rt-mutex itself it propagates the priority
40 RT-mutexes are optimized for fastpath operations and have no internal
43 support. [If that is not available then the rt-mutex internal spinlock
46 The state of the rt-mutex is tracked via the owner field of the rt-mutex
|
| D | index.rst | 14 rt-mutex-design
15 rt-mutex
|
| D | rt-mutex-design.rst | 2 RT-mutex implementation design
12 Documentation/locking/rt-mutex.rst. Although this document does explain problems
311 See Documentation/locking/rt-mutex.rst for further details.
|
| /Documentation/arm/ |
| D | vlocks.rst | 133 LDR Rt, [Rn]
134 CMP Rt, #0
138 LDRB Rt, [Rn]
139 CMP Rt, #0
140 LDRBEQ Rt, [Rn, #1]
141 CMPEQ Rt, #0
142 LDRBEQ Rt, [Rn, #2]
143 CMPEQ Rt, #0
144 LDRBEQ Rt, [Rn, #3]
145 CMPEQ Rt, #0
[all …]
|
| /Documentation/ |
| D | pi-futex.txt | 39 I.e. critical RT apps often choose lock structures to protect critical
67 [this is a quite common scenario for most non-trivial RT applications],
95 the futex-queue. The pi_state includes an rt-mutex, which is a PI-aware,
97 of the rt-mutex, and the FUTEX_WAITERS bit is atomically set in the
98 futex value. Then this task tries to lock the rt-mutex, on which it
122 Documentation/locking/rt-mutex.rst.
|
| D | futex-requeue-pi.txt | 8 boosting logic [see rt-mutex-desgin.txt] For the purposes of
|
| /Documentation/scheduler/ |
| D | sched-deadline.rst | 33 system behavior. As for -rt (group) scheduling, it is assumed that root users
216 - Umax is the maximum reclaimable utilization (subjected to RT throttling
221 (subjected to RT throttling limits).
566 to -deadline tasks is similar to the one already used for -rt
567 tasks with real-time group scheduling (a.k.a. RT-throttling - see
568 Documentation/scheduler/sched-rt-group.rst), and is based on readable/
575 A main difference between deadline bandwidth management and RT-throttling
576 is that -deadline tasks have bandwidth on their own (while -rt ones don't!),
591 For now the -rt knobs are used for -deadline admission control and the
592 -deadline runtime is accounted against the -rt runtime. We realize that this
[all …]
|
| D | index.rst | 17 sched-rt-group
|
| D | sched-design-CFS.rst | 136 SCHED_FIFO/_RR are implemented in sched/rt.c and are as specified by
154 sched/rt.c implements SCHED_FIFO and SCHED_RR semantics, in a simpler way than
155 the previous vanilla scheduler did. It uses 100 runqueues (for all 100 RT
|
| D | sched-nice-design.rst | 84 run audio (and other multimedia) apps under RT priorities such as
|
| D | sched-rt-group.rst | 110 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
|
| D | sched-bwc.rst | 6 The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.rst ]
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | ti,secure-proxy.txt | 17 rt - Map the realtime status region
34 reg-names = "target_data", "rt", "scfg";
|
| /Documentation/devicetree/bindings/input/touchscreen/ |
| D | tsc2007.txt | 14 - ti,max-rt: maximum pressure.
|
| /Documentation/block/ |
| D | ioprio.rst | 24 care, one io RT process can starve the entire system. Within the RT class,
|
| /Documentation/trace/ |
| D | hwlat_detector.rst | 13 originally written for use by the "RT" patch since the Real Time
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi-pl022.yaml | 52 pl022,rt:
|
| /Documentation/RCU/ |
| D | rcubarrier.txt | 319 Currently, -rt implementations of RCU keep but a single global
321 problem. However, when the -rt RCU eventually does have per-CPU
|
| D | whatisRCU.txt | 936 b. What about the -rt patchset? If readers would need to block
937 in an non-rt kernel, you need SRCU. If readers would block
938 in a -rt kernel, but not in a non-rt kernel, SRCU is not
939 necessary. (The -rt patchset turns spinlocks into sleeplocks,
|
| /Documentation/driver-api/gpio/ |
| D | driver.rst | 332 threaded on -RT. As a result, spinlock_t or any sleepable APIs (like PM
337 this way it will become a threaded IRQ handler on -RT and a hard IRQ handler
338 on non-RT (for example, see [3]).
362 Realtime considerations: this kind of handlers will be forced threaded on -RT,
|
| /Documentation/networking/ |
| D | radiotap-headers.txt | 139 } /* while more rt headers */
|
| D | rxrpc.txt | 334 RXRPC_ACK -rt n/a Final ACK received
335 RXRPC_NET_ERROR -rt error num Network error on call
336 RXRPC_BUSY -rt n/a Call rejected (server busy)
337 RXRPC_LOCAL_ERROR -rt error num Local error encountered
|
| /Documentation/admin-guide/ |
| D | sysrq.rst | 34 256 = 0x100 - allow nicing of all RT tasks
115 ``n`` Used to make RT tasks nice-able
|
| /Documentation/x86/ |
| D | earlyprintk.rst | 141 …sks(I) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff sh…
|
| /Documentation/core-api/ |
| D | local_ops.rst | 78 -rt kernels.
|
12