| /linux/Documentation/scheduler/ |
| H A D | sched-capacity.rst | 127 2. Task utilization
135 while task utilization is specific to CFS, it is convenient to describe it here
138 Task utilization is a percentage meant to represent the throughput requirements
143 On an SMP system with fixed frequencies, 100% utilization suggests the task is a
144 busy loop. Conversely, 10% utilization hints it is a small periodic task that
173 The task utilization signal can be made frequency invariant using the following
179 task utilization of 25%.
184 CPU capacity has a similar effect on task utilization in that running an
211 The task utilization signal can be made CPU invariant using the following
218 invariant task utilization of 25%.
[all …]
|
| H A D | sched-energy.rst | 75 normalized in a 1024 range, and are comparable with the utilization signals of
77 to capacity and utilization values, EAS is able to estimate how big/busy a
135 for the CPU with the highest spare capacity (CPU capacity - CPU utilization) in
143 looks at the current utilization landscape of the CPUs and adjusts it to
146 the given utilization landscape.
158 The current utilization landscape of the CPUs is depicted on the graph
188 compared to leaving P on CPU0. EAS assumes that OPPs follow utilization
253 bigs, for example. So, if the little CPUs happen to have enough utilization at
274 impact on throughput for high-utilization scenarios, EAS also implements another
275 mechanism called 'over-utilization'.
[all …]
|
| H A D | sched-nice-design.rst | 46 a CPU utilization, but because it causes too frequent (once per
52 right minimal granularity - and this translates to 5% CPU utilization.
55 terms of CPU utilization, we only got complaints about it (still) being
99 the new scheduler makes nice(1) have the same CPU utilization effect on
102 utilization "split" between them as running a nice -5 and a nice -4
|
| H A D | schedutil.rst | 90 - Documentation/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utilization"
97 though when running their expected utilization will be the same, they suffer a
128 the frequency invariant utilization estimate of the CPU. From this we compute
162 will closely reflect utilization.
|
| H A D | sched-util-clamp.rst | 22 point; hence the name. That is, by clamping utilization we are making the
39 the uclamp values as performance points rather than utilization is a better
83 how scheduler utilization signal is calculated**.
122 its utilization signal; acting as a bias mechanism that influences certain
125 The actual utilization signal of a task is never clamped in reality. If you
133 which have implications on the utilization value at CPU runqueue (rq for short)
136 When a task wakes up on an rq, the utilization signal of the rq will be
148 The way this is handled is by dividing the utilization range into buckets
211 an rq as tasks are enqueued/dequeued, the whole utilization range is divided
350 For example, the following scenario have 40% to 80% utilization constraints:
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-driver-qat_telemetry | 42 Reads report metrics about performance and utilization of
64 util_cpr<N> utilization of Compression slice N [%]
66 util_xlt<N> utilization of Translator slice N [%]
68 util_dcpr<N> utilization of Decompression slice N [%]
70 util_pke<N> utilization of PKE N [%]
72 util_ucs<N> utilization of UCS slice N [%]
74 util_wat<N> utilization of Wireless Authentication
78 util_wcp<N> utilization of Wireless Cipher slice N [%]
80 util_cph<N> utilization of Cipher slice N [%]
82 util_ath<N> utilization of Authentication slice N [%]
[all …]
|
| H A D | sysfs-driver-genwqe | 50 Used for performance and utilization measurements.
56 Used for performance and utilization measurements.
|
| H A D | sysfs-driver-intel_sdsi | 79 utilization metrics of On Demand enabled features. Mailbox
|
| H A D | sysfs-class-devfreq | 126 monitor the device status such as utilization. The user
|
| /linux/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/ |
| H A D | gk20a.c | 125 u32 utilization = 0; in gk20a_pmu_dvfs_work() local
138 utilization = div_u64((u64)status.busy * 100, status.total); in gk20a_pmu_dvfs_work()
140 data->avg_load = (data->p_smooth * data->avg_load) + utilization; in gk20a_pmu_dvfs_work()
143 utilization, data->avg_load); in gk20a_pmu_dvfs_work()
|
| /linux/Documentation/admin-guide/pm/ |
| H A D | intel_uncore_frequency_scaling.rst | 126 The hardware monitors the average CPU utilization across all cores
136 If the average CPU utilization is below a user-defined threshold
141 Similarly in high load scenario where the CPU utilization goes above
145 immediately with CPU utilization spikes.
156 threshold. This attribute is in percentages of CPU utilization.
160 threshold. This attribute is in percentages of CPU utilization.
167 * when CPU utilization is less than 10%: sets uncore frequency to 800MHz
168 * when CPU utilization is higher than 95%: increases uncore frequency in
|
| H A D | cpufreq.rst | 42 the utilization of the system generally changes over time, that has to be done
156 That callback is expected to register per-CPU utilization update callbacks for
158 The utilization update callbacks will be invoked by the CPU scheduler on
160 scheduler tick or generally whenever the CPU utilization may change (from the
185 to register per-CPU utilization update callbacks for each policy. These
391 This governor uses CPU utilization data available from the CPU scheduler. It
401 invoking its utilization update callback for that CPU. If it is invoked by the
406 given CPU as the CPU utilization estimate (see the *Per-entity load tracking*
438 utilization metric, so in principle its decisions should not contradict the
|
| H A D | intel_pstate.rst | 112 ``intel_pstate`` registers utilization update callbacks with the CPU scheduler
155 In this mode ``intel_pstate`` registers utilization update callbacks with the
160 periodically updated by those utilization update callbacks too.
181 utilization metric used by it is based on numbers coming from feedback
183 current CPU utilization.
185 This algorithm is run by the driver's utilization update callback for the
225 utilization update callbacks with the CPU scheduler and the ``scaling_cur_freq``
491 driver's utilization update callback by the CPU scheduler for that CPU.
|
| /linux/drivers/devfreq/event/ |
| H A D | Kconfig | 12 (e.g., raw data, utilization, latency, bandwidth). The events
33 utilization of each module.
|
| /linux/drivers/cpufreq/ |
| H A D | Kconfig | 151 changes frequency based on the CPU utilization.
195 This governor makes decisions based on the utilization data provided
197 the utilization/capacity ratio coming from the scheduler. If the
198 utilization is frequency-invariant, the new frequency is also
201 frequency tipping point is at utilization/capacity equal to 80% in
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| H A D | e1000e.rst | 54 increased CPU utilization, though it may help throughput in some circumstances.
59 load on the system and can lower CPU utilization under heavy load,
85 to the increased CPU utilization of the higher interrupt rate.
88 very low latency. This can sometimes cause extra CPU utilization. If
107 system and can lower CPU utilization under heavy load, but will increase
|
| H A D | e1000.rst | 106 load on the system and can lower CPU utilization under heavy load,
170 are in use simultaneously, the CPU utilization may increase non-
171 linearly. In order to limit the CPU utilization without impacting
181 be platform-specific. If CPU utilization is not a concern, use
194 incoming packets, at the expense of increased system memory utilization.
|
| /linux/Documentation/translations/zh_CN/scheduler/ |
| H A D | schedutil.rst | 89 …cumentation/translations/zh_CN/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utilization"
|
| /linux/Documentation/networking/ |
| H A D | mpls-sysctl.rst | 15 A dense utilization of the entries in the platform label table
|
| H A D | mptcp-sysctl.rst | 105 an high value maximize links utilization on edge scenarios e.g. lossy
|
| /linux/drivers/gpu/drm/display/ |
| H A D | Kconfig | 53 BW utilization for display streams on Thunderbolt links.
|
| /linux/Documentation/scsi/ |
| H A D | g_NCR5380.rst | 19 allow targets to disconnect and thereby improve SCSI bus utilization.
|
| /linux/Documentation/gpu/ |
| H A D | drm-usage-stats.rst | 128 utilization can be calculated entirely on the GPU clock domain, without
138 percentage utilization of the engine, whereas drm-engine-<keystr> only reflects
|
| /linux/fs/proc/ |
| H A D | Kconfig | 107 Various /proc files exist to monitor process memory utilization:
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | cache-policies.rst | 50 The smq policy (vs mq) offers the promise of less memory utilization,
|