Searched full:priority (Results 1 – 25 of 165) sorted by relevance
1234567
| /Documentation/virt/kvm/devices/ |
| D | xics.txt | 26 * Pending interrupt priority, 8 bits
27 Zero is the highest priority, 255 means no interrupt is pending.
29 * Pending IPI (inter-processor interrupt) priority, 8 bits
30 Zero is the highest priority, 255 means no IPI is pending.
35 * Current processor priority, 8 bits
36 Zero is the highest priority, meaning no interrupts can be
37 delivered, and 255 is the lowest priority.
49 * Priority, 8 bits
50 This is the priority specified for this interrupt source, where 0 is
51 the highest priority and 255 is the lowest. An interrupt with a
[all …]
|
| D | xive.txt | 26 handle priority management and interrupt acknowledgment. The most
30 - Current Processor Priority (CPPR)
102 values: | eisn | mask | server | priority
103 - priority: 0-7 interrupt priority level
110 -EINVAL: Invalid priority
121 The EQ descriptor identifier is a tuple (server, priority) :
123 values: | unused | server | priority
144 -EINVAL: Invalid priority
|
| /Documentation/locking/ |
| D | rt-mutex.rst | 5 RT-mutexes with priority inheritance are used to support PI-futexes,
6 which enable pthread_mutex_t priority inheritance attributes
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
23 priority boosting is immediately removed once the rt_mutex has been
27 mutexes which protect shared resources. Priority inheritance is not a
30 an high priority thread, without losing determinism.
33 priority order. For same priorities FIFO order is chosen. For each
[all …]
|
| D | rt-mutex-design.rst | 16 The goal of this document is to help others understand the priority
21 Unbounded Priority Inversion
24 Priority inversion is when a lower priority process executes while a higher
25 priority process wants to run. This happens for several reasons, and
26 most of the time it can't be helped. Anytime a high priority process wants
27 to use a resource that a lower priority process has (a mutex for example),
28 the high priority process must wait until the lower priority process is done
29 with the resource. This is a priority inversion. What we want to prevent
30 is something called unbounded priority inversion. That is when the high
31 priority process is prevented from running by a lower priority process for
[all …]
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-g-priority.rst | 19 VIDIOC_G_PRIORITY - VIDIOC_S_PRIORITY - Query or request the access priority associated with a file…
45 To query the current access priority applications call the
47 variable where the driver stores the current priority.
49 To request an access priority applications store the desired priority in
68 - Lowest priority, usually applications running in background, for
71 read from a device at this priority.
77 - Medium priority, usually applications started and interactively
80 controls. This is the default priority unless an application
84 - Highest priority. Only one file descriptor can have this priority,
97 The requested priority value is invalid.
[all …]
|
| D | app-pri.rst | 13 Application Priority
20 channel. Another objective is to permit low priority applications
28 query the access priority associate with a file descriptor. Opening a
29 device assigns a medium priority, compatible with earlier versions of
31 different priority will usually call :ref:`VIDIOC_S_PRIORITY
37 after another application obtained higher priority.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_prio.rst | 2 Network priority cgroup
5 The Network priority cgroup provides an interface to allow an administrator to
6 dynamically set the priority of network traffic generated by various
9 Nominally, an application would set the priority of its traffic via the
13 2) The priority of application traffic is often a site-specific administrative
17 the priority of egress traffic on a given interface. Network priority groups can
36 It contains a list of tuples in the form <ifname priority>. Contents of this
43 iscsi net_prio cgroup and egressing on interface eth0 to have the priority of
46 priority.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | ti,c64x+megamod-pic.txt | 7 C64X+ core. Priority 0 and 1 are used for reset and NMI respectively.
8 Priority 2 and 3 are reserved. Priority 4-15 are used for interrupt
18 Single cell specifying the core interrupt priority level (4-15) where
19 4 is highest priority and 15 is lowest priority.
37 One for each core interrupt priority level. In addition to the combined
50 The cells contain the core priority interrupt to which the
56 priority interrupts. The first cell corresponds to
57 core priority 4 and the last cell corresponds to
58 core priority 15. The value of each cell is the
70 be the core priority level, not the megamodule interrupt number.
[all …]
|
| D | arm,nvic.txt | 5 vary in the number of interrupts and priority bits per interrupt.
19 The 2nd cell is the priority of the interrupt.
24 - arm,num-irq-priority-bits: The number of priority bits implemented by the
35 arm,num-irq-priority-bits = <4>;
|
| D | sifive,plic-1.0.0.txt | 16 Each interrupt has a configurable priority. Higher priority interrupts are
17 serviced first. Each context can specify a priority threshold. Interrupts
18 with priority below this threshold will not cause the PLIC to raise its
|
| /Documentation/vm/ |
| D | swap_numa.rst | 15 Swap device has priority and that decides the order of it to be used. To make
16 use of automatically binding, there is no need to manipulate priority settings
65 The current code uses a priority based list, swap_avail_list, to decide
67 priority, they are used round robin. This change here replaces the single
69 it sees its own priority based list of available swap devices. Swap
70 device's priority can be promoted on its matching node's swap_avail_list.
72 The current swap device's priority is set as: user can set a >=0 value,
73 or the system will pick one starting from -1 then downwards. The priority
76 the semantics for priority >=0 cases, the previous starting from -1 then
79 node, they will all be promoted to priority -1 on that node's plist and will
|
| /Documentation/devicetree/bindings/dma/ |
| D | snps,dw-axi-dmac.txt | 12 - snps,priority: Priority of channel. Array size is equal to the number of
13 dma-channels. Priority value must be programmed within [0:dma-channels-1]
14 range. (0 - minimum priority)
37 snps,priority = <0 1 2 3>;
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | gpio-restart.txt | 11 priority order. The gpio is configured as an output, and driven active,
31 - priority : A priority ranging from 0 to 255 (default 128) according to
38 255: Highest priority restart handler, will preempt all other
50 priority = <128>;
|
| /Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.txt | 38 - nvidia,priority: Each throttles has its own throttle settings, so the
41 Bigger value indicates higher priority, In general, higher priority
43 thermal alarms are given higher priority, and ensure that there is
44 no race if priority of two vectors is set to the same value.
126 nvidia,priority = <100>;
139 nvidia,priority = <80>;
148 * arbiter will select the highest priority as the final throttle
153 nvidia,priority = <50>;
179 nvidia,priority = <100>;
190 nvidia,priority = <80>;
[all …]
|
| /Documentation/ |
| D | pi-futex.txt | 20 Priority Inheritance - why?
45 design with multiple tasks (with multiple priority levels) sharing
49 we've got even more priority levels.
57 Most of the technical counter-arguments against doing priority
61 does not apply (user-space spinlocks have the same priority inversion
64 locks (such as futex-based pthread mutexes) is priority inheritance:
71 deterministic execution of the high-prio task: any medium-priority task
121 More details about priority inheritance can be found in
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | mtk-gce.txt | 18 <&phandle channel priority atomic_exec>
21 priority: Priority of GCE thread.
40 or 'dt-binding/gce/mt8183-gce.h'. Such as sub-system ids, thread priority, event ids.
|
| /Documentation/ABI/testing/ |
| D | sysfs-platform-hidma-mgmt | 1 What: /sys/devices/platform/hidma-mgmt*/chanops/chan*/priority
2 /sys/devices/platform/QCOM8060:*/chanops/chan*/priority
8 low priority (0) or high priority (1) channel.
17 equal priority channels during round robin scheduling.
|
| D | sysfs-bus-coresight-devices-funnel | 8 What: /sys/bus/coresight/devices/<memory_map>.funnel/priority
12 Description: (RW) Defines input port priority order.
|
| D | dev-kmsg | 13 carries the syslog priority and facility. The single decimal
15 priority and the next 8 bits the syslog facility number.
17 If no prefix is given, the priority number is the default kernel
18 log priority and the facility number is set to LOG_USER (1). It
60 prefix including priority and facility, the 64 bit message
|
| /Documentation/devicetree/bindings/bus/ |
| D | ti,da850-mstpri.txt | 2 priority driver
4 DA8XX SoCs feature a set of registers allowing to change the priority of all
|
| /Documentation/RCU/ |
| D | torture.txt | 67 used to force RCU priority inversion. This value should be zero.
70 used to force RCU priority inversion, it was unable to set them
71 to the real-time priority level of 1. This value should be zero.
73 o "rtbf": The number of times that RCU priority boosting failed
74 to resolve RCU priority inversion.
77 an RCU priority inversion condition. If you are testing RCU
78 priority boosting via the "test_boost" module parameter, this
|
| /Documentation/devicetree/bindings/c6x/ |
| D | emifa.txt | 20 - ti,emifa-burst-priority:
21 Number of memory transfers after which the EMIF will elevate the priority
42 ti,emifa-burst-priority = <255>;
|
| /Documentation/devicetree/bindings/usb/ |
| D | lpc32xx-udc.txt | 8 * USB Device Low Priority Interrupt
9 * USB Device High Priority Interrupt
|
| /Documentation/block/ |
| D | ioprio.rst | 22 higher priority than any other in the system, processes from this class are
31 for any process that hasn't set a specific io priority. The class data
48 If pid isn't given, the current process is assumed. IO priority settings
54 will run ls at the best-effort scheduling class at the highest priority.
59 will change pid 100 to run at the realtime scheduling class, at priority 2.
|
| /Documentation/devicetree/bindings/net/ |
| D | snps,dwmac.yaml | 146 * snps,rx-sched-sp, Strict priority
147 * snps,rx-sched-wsp, Weighted Strict priority
159 * snps,priority, RX queue priority (Range 0x0 to 0xF)
172 * snps,tx-sched-sp, Strict priority
186 * snps,priority, TX queue priority (Range 0x0 to 0xF)
371 snps,priority = <0x0>;
381 snps,priority = <0x0>;
390 snps,priority = <0x1>;
|
1234567