Searched full:priority (Results 1 – 25 of 241) sorted by relevance
12345678910
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-priority.rst | 13 VIDIOC_G_PRIORITY - VIDIOC_S_PRIORITY - Query or request the access priority associated with a file…
38 To query the current access priority applications call the
40 variable where the driver stores the current priority.
42 To request an access priority applications store the desired priority in
60 - Lowest priority, usually applications running in background, for
63 read from a device at this priority.
69 - Medium priority, usually applications started and interactively
72 controls. This is the default priority unless an application
76 - Highest priority. Only one file descriptor can have this priority,
88 The requested priority value is invalid.
[all …]
|
| D | app-pri.rst | 6 Application Priority
13 channel. Another objective is to permit low priority applications
21 query the access priority associate with a file descriptor. Opening a
22 device assigns a medium priority, compatible with earlier versions of
24 different priority will usually call :ref:`VIDIOC_S_PRIORITY
30 after another application obtained higher 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 …]
|
| D | pi-futex.rst | 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
|
| D | locktypes.rst | 101 RT-mutexes are mutexes with support for priority inheritance (PI).
127 providing priority inheritance for semaphores. After all, an unknown
129 result in priority inversion.
150 Because an rw_semaphore writer cannot grant its priority to multiple
151 readers, a preempted low-priority reader will continue holding its lock,
152 thus starving even high-priority writers. In contrast, because readers
153 can grant their priority to a writer, a preempted low-priority writer will
154 have its priority boosted until it releases the lock, thus preventing that
313 - Because an rwlock_t writer cannot grant its priority to multiple
314 readers, a preempted low-priority reader will continue holding its lock,
[all …]
|
| /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/virt/kvm/devices/ |
| D | xics.rst | 47 * Pending interrupt priority, 8 bits
48 Zero is the highest priority, 255 means no interrupt is pending.
50 * Pending IPI (inter-processor interrupt) priority, 8 bits
51 Zero is the highest priority, 255 means no IPI is pending.
56 * Current processor priority, 8 bits
57 Zero is the highest priority, meaning no interrupts can be
58 delivered, and 255 is the lowest priority.
71 * Priority, 8 bits
73 This is the priority specified for this interrupt source, where 0 is
74 the highest priority and 255 is the lowest. An interrupt with a
[all …]
|
| D | xive.rst | 29 handle priority management and interrupt acknowledgment. The most
33 - Current Processor Priority (CPPR)
131 values: | eisn | mask | server | priority
133 - priority: 0-7 interrupt priority level
143 -EINVAL Invalid priority
157 The EQ descriptor identifier is a tuple (server, priority)::
160 values: | unused | server | priority
187 -EINVAL Invalid priority
|
| /Documentation/admin-guide/mm/ |
| D | swap_numa.rst | 13 Swap device has priority and that decides the order of it to be used. To make
14 use of automatically binding, there is no need to manipulate priority settings
63 The current code uses a priority based list, swap_avail_list, to decide
65 priority, they are used round robin. This change here replaces the single
67 it sees its own priority based list of available swap devices. Swap
68 device's priority can be promoted on its matching node's swap_avail_list.
70 The current swap device's priority is set as: user can set a >=0 value,
71 or the system will pick one starting from -1 then downwards. The priority
74 the semantics for priority >=0 cases, the previous starting from -1 then
77 node, they will all be promoted to priority -1 on that node's plist and will
|
| /Documentation/networking/ |
| D | tc-queue-filters.rst | 13 using the action skbedit priority for Tx priority selection,
14 the priority maps to a traffic class (set of queues) when
34 pipeline resolves conflicts based on priority. On Intel E810
36 priority over flow director filter assigning a queue. The hash
37 filter has lowest priority.
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| 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>;
|
| /Documentation/admin-guide/pm/ |
| D | intel-speed-select.rst | 324 allows users to define per core priority. This defines a mechanism to distribute
331 service and hence an associated priority. The granularity is at core level not
338 and use a priority type. There is a default per platform priority type, which
347 Clos Enable: Specify priority type with [--priority|-p]
350 There are two types of priority types:
354 Priority for ordered throttling is defined based on the index of the assigned
355 CLOS group. Where CLOS0 gets highest priority (throttled last).
357 Priority order is:
362 When proportional priority is used, there is an additional parameter called
364 proportional priority is to provide each core with the requested min., then
[all …]
|
| /Documentation/networking/devlink/ |
| D | prestera.rst | 81 - Traps packets that have ACL priority set to 0 (tc pref 0)
84 - Traps packets that have ACL priority set to 1 (tc pref 1)
87 - Traps packets that have ACL priority set to 2 (tc pref 2)
90 - Traps packets that have ACL priority set to 3 (tc pref 3)
93 - Traps packets that have ACL priority set to 4 (tc pref 4)
96 - Traps packets that have ACL priority set to 5 (tc pref 5)
99 - Traps packets that have ACL priority set to 6 (tc pref 6)
102 - Traps packets that have ACL priority set to 7 (tc pref 7)
|
| /Documentation/gpu/rfc/ |
| D | i915_scheduler.rst | 50 * Port i915 priority inheritance / boosting feature in DRM scheduler
58 * Pull out i915 priority levels and use DRM priority levels
72 This attribute indicates the 2k i915 user priority levels are statically mapped
75 * -1k to -1 Low priority
76 * 0 Medium priority
77 * 1 to 1k High priority
79 This is needed because the GuC only has 4 priority bands. The highest priority
80 band is reserved with the kernel. This aligns with the DRM scheduler priority
86 …https://www.khronos.org/registry/vulkan/specs/1.2-extensions/html/chap5.html#devsandqueues-priority
87 * https://spec.oneapi.com/level-zero/latest/core/api.html#ze-command-queue-priority-t
|
| /Documentation/ABI/testing/ |
| D | sysfs-block-device | 59 command queueing) priority support. By default this feature is
61 priority feature, writing "1" to this file results in an error
72 (HBA) implementing support for the SATA NCQ priority feature.
74 support for the SATA NCQ priority feature, regardless of the
84 command queueing) priority feature.
94 (HBA) implementing support for the SATA NCQ priority feature.
96 support for the SATA NCQ priority feature, regardless of the
|
| 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 | 14 carries the syslog priority and facility. The single decimal
16 priority and the next 8 bits the syslog facility number.
18 If no prefix is given, the priority number is the default kernel
19 log priority and the facility number is set to LOG_USER (1). It
74 prefix including priority and facility, the 64 bit message
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | restart-handler.yaml | 18 priority:
21 A priority ranging from 0 to 255 according to the following guidelines::
26 255:: Highest priority restart handler, will preempt all other restart handlers.
|
| /Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.yaml | 77 nvidia,priority:
84 higher priority, In general, higher priority translates to lower
86 alarms are given higher priority, and ensure that there is no
87 race if priority of two vectors is set to the same value.
268 nvidia,priority = <100>;
281 nvidia,priority = <80>;
290 * arbiter will select the highest priority as the final throttle
295 nvidia,priority = <50>;
329 nvidia,priority = <100>;
340 nvidia,priority = <80>;
[all …]
|
| /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/block/ |
| D | ioprio.rst | 9 The io priority feature enables users to io nice processes or process groups,
21 higher priority than any other in the system, processes from this class are
30 for any process that hasn't set a specific io priority. The class data
47 If pid isn't given, the current process is assumed. IO priority settings
53 will run ls at the best-effort scheduling class at the highest priority.
58 will change pid 100 to run at the realtime scheduling class, at priority 2.
|
| /Documentation/devicetree/bindings/dma/stm32/ |
| D | st,stm32-dma3.yaml | 61 -bit 0-1: The priority level
62 0x0: low priority, low weight
63 0x1: low priority, mid weight
64 0x2: low priority, high weight
65 0x3: high priority
|
| /Documentation/devicetree/bindings/net/ |
| D | intel,dwmac-plat.yaml | 74 snps,priority = <0x0>;
80 snps,priority = <0x1>;
90 snps,priority = <0x0>;
96 snps,priority = <0x1>;
|
12345678910