| /linux/include/uapi/linux/sched/ |
| H A D | types.h | 73 * Task Utilization Attributes
76 * A subset of sched_attr attributes allows to specify the utilization
78 * the utilization boundaries within which it should schedule the task. These
82 * @sched_util_min represents the minimum utilization
83 * @sched_util_max represents the maximum utilization
85 * Utilization is a value in the range [0..SCHED_CAPACITY_SCALE]. It
88 * 20% utilization task is a task running for 2ms every 10ms at maximum
91 * A task with a min utilization value bigger than 0 is more likely scheduled
93 * A task with a max utilization value smaller than 1024 is more likely
96 * A task utilization boundary can be reset by setting the attribute to -1.
[all …]
|
| /linux/drivers/crypto/intel/qat/qat_common/ |
| H A D | adf_gen4_tl.h | 30 * @reg_tm_slice_util: Slice utilization.
59 * @ath_slices: array of Authentication slices utilization registers
60 * @cph_slices: array of Cipher slices utilization registers
61 * @cpr_slices: array of Compression slices utilization registers
62 * @xlt_slices: array of Translator slices utilization registers
63 * @dcpr_slices: array of Decompression slices utilization registers
64 * @pke_slices: array of PKE slices utilization registers
65 * @ucs_slices: array of UCS slices utilization registers
66 * @wat_slices: array of Wireless Authentication slices utilization registers
67 * @wcp_slices: array of Wireless Cipher slices utilization registers
|
| H A D | adf_gen4_tl.c | 62 /* Slice utilization counters. */
64 /* Compression slice utilization. */
66 /* Translator slice utilization. */
68 /* Decompression slice utilization. */
70 /* PKE utilization. */
72 /* Wireless Authentication slice utilization. */
74 /* Wireless Cipher slice utilization. */
76 /* UCS slice utilization. */
78 /* Cipher slice utilization. */
80 /* Authentication slice utilization. */
|
| /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 | sched-util-clamp.rst | 4 Utilization Clamping
10 Utilization clamping, also known as util clamp or uclamp, is a scheduler
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
[all …]
|
| 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.
|
| /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
|
| /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.
|
| /linux/drivers/gpu/drm/amd/include/ |
| H A D | kgd_pp_interface.h | 360 /* Utilization Instantaneous (%) */
364 /* Utilization Accumulated (%) */
369 /* Utilization Instantaneous (%) */
373 /* Utilization Accumulated (%) */
521 /* Utilization */
570 /* Utilization */
629 /* Utilization */
691 /* Utilization */
763 /* Utilization (%) */
788 /* Utilization Accumulated (%) */
[all …]
|
| /linux/kernel/sched/ |
| H A D | cpufreq_schedutil.c | 3 * CPUFreq governor based on scheduler-provided CPU utilization data.
146 * @util: Current CPU utilization.
149 * If the utilization is frequency-invariant, choose the new frequency to be
154 * Otherwise, approximate the would-be frequency-invariant utilization by
185 /* Add dvfs headroom to actual utilization */ in sugov_effective_cpu_perf()
242 * Each time a task wakes up after an IO operation, the CPU utilization can be
243 * boosted to a certain utilization which doubles at each "frequent and
244 * successive" wakeup from IO, ranging from IOWAIT_BOOST_MIN to the utilization
248 * otherwise we restart from the utilization of the minimum OPP.
287 * utilization boosted to speed up the completion of those IO operations.
[all …]
|
| H A D | deadline.c | 333 * will not touch the rq's active utilization, in dl_rq_change_utilization()
381 * The utilization of a task cannot be immediately removed from
382 * the rq active utilization (running_bw) when the task blocks.
392 * task's utilization has to be added to running_bw again.
398 * "ACTIVE" when its utilization contributes to running_bw; an
465 * utilization now, instead of starting a timer in task_non_contending()
518 * will not touch the rq's active utilization, in task_contending()
525 * task's utilization has already been removed from in task_contending()
526 * active utilization (either when the task blocked, in task_contending()
1431 * where u is the utilization of the task, Umax is the maximum reclaimable
[all …]
|
| H A D | fair.c | 101 * The margin used when comparing utilization with CPU capacity.
1067 * only 1/2 of the left utilization budget:
3994 * thread is a different class (!fair), nor will the utilization in cfs_rq_util_change()
4281 /* Set new sched_entity's utilization */ in update_tg_cfs_util()
4287 /* Update parent cfs_rq utilization */ in update_tg_cfs_util()
4429 * Check if we need to update the load and the utilization of a blocked
4437 * If sched_entity still have not zero load or utilization, we have to in skip_blocked_update()
4445 * the utilization of the sched_entity: in skip_blocked_update()
4451 * Otherwise, the load and the utilization of the sched_entity is in skip_blocked_update()
4849 /* Update root cfs_rq's estimated utilization */ in util_est_enqueue()
[all …]
|
| /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()
142 nvkm_trace(subdev, "utilization = %d %%, avg_load = %d %%\n", in gk20a_pmu_dvfs_work()
143 utilization, data->avg_load); in gk20a_pmu_dvfs_work()
|
| /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/drivers/devfreq/event/ |
| H A D | Kconfig | 12 (e.g., raw data, utilization, latency, bandwidth). The events
33 utilization of each module.
|
| /linux/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| H A D | ehl-metrics.json | 39 "BriefDescription": "Average CPU Utilization",
49 "BriefDescription": "Average Frequency Utilization relative nominal frequency",
|
| /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/drivers/thermal/ |
| H A D | devfreq_cooling.c | 39 * @res_util: Resource utilization scaling factor for the power.
42 * 'utilization' (which is 'busy_time' / 'total_time').
251 /* Scale power for utilization */ in devfreq_cooling_get_requested_power()
305 /* Scale for resource utilization */ in devfreq_cooling_power2state()
309 /* Scale dynamic power for utilization */ in devfreq_cooling_power2state()
|
| /linux/Documentation/gpu/ |
| H A D | drm-usage-stats.rst | 81 Utilization subsection
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/tools/perf/tests/shell/base_report/ |
| H A D | test_basic.sh | 30 ../common/check_all_patterns_found.pl "input" "verbose" "show-nr-samples" "show-cpu-utilization" "threads" "comms" "pid" "tid" "dsos" "symbols" "symbol-filter" < $LOGS_DIR/basic_helpmsg.log
124 ### show CPU utilization
137 print_results $PERF_EXIT_CODE $CHECK_EXIT_CODE "show CPU utilization"
|