| /Linux-v5.4/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/ |
| 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-v5.4/Documentation/scheduler/ |
| 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 …]
|
| 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
|
| D | sched-deadline.rst | 183 the task's utilization must be removed from the previous runqueue's active
184 utilization and must be added to the new runqueue's active utilization.
192 its utilization is removed from the runqueue's active utilization.
195 its utilization is added to the active utilization of the runqueue where
216 - Umax is the maximum reclaimable utilization (subjected to RT throttling
218 - Uinact is the (per runqueue) inactive utilization, computed as
220 - Uextra is the (per runqueue) extra reclaimable utilization
340 The utilization of a real-time task is defined as the ratio between its
344 If the total utilization U=sum(WCET_i/P_i) is larger than M (with M equal
347 Note that total utilization is defined as the sum of the utilizations
[all …]
|
| /Linux-v5.4/drivers/devfreq/event/ |
| D | Kconfig | 12 (e.g., raw data, utilization, latency, bandwidth). The events
33 utilization of each module.
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-driver-genwqe | 46 Used for performance and utilization measurements.
52 Used for performance and utilization measurements.
|
| /Linux-v5.4/drivers/cpufreq/ |
| D | Kconfig | 149 changes frequency based on the CPU utilization.
191 This governor makes decisions based on the utilization data provided
193 the utilization/capacity ratio coming from the scheduler. If the
194 utilization is frequency-invariant, the new frequency is also
197 frequency tipping point is at utilization/capacity equal to 80% in
|
| /Linux-v5.4/fs/f2fs/ |
| D | debug.c | 100 si->utilization = utilization(sbi); in update_general_status()
302 si->utilization, si->valid_count, si->discard_blks); in stat_show()
305 si->utilization, si->valid_count); in stat_show()
|
| /Linux-v5.4/Documentation/networking/ |
| D | mpls-sysctl.txt | 8 A dense utilization of the entries in the platform label table
|
| D | xfrm_device.txt | 15 can radically increase throughput and decrease CPU utilization. The XFRM
|
| /Linux-v5.4/Documentation/networking/device_drivers/intel/ |
| 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
|
| 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.
|
| D | fm10k.rst | 93 utilization can be significantly reduced when under large Rx load. GRO is an
|
| /Linux-v5.4/include/uapi/misc/ |
| D | habanalabs.h | 148 __u32 utilization; member
|
| /Linux-v5.4/Documentation/scsi/ |
| D | g_NCR5380.txt | 13 allow targets to disconnect and thereby improve SCSI bus utilization.
|
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 43 the utilization of the system generally changes over time, that has to be done
157 That callback is expected to register per-CPU utilization update callbacks for
159 The utilization update callbacks will be invoked by the CPU scheduler on
161 scheduler tick or generally whenever the CPU utilization may change (from the
186 to register per-CPU utilization update callbacks for each policy. These
388 This governor uses CPU utilization data available from the CPU scheduler. It
398 invoking its utilization update callback for that CPU. If it is invoked by the
403 given CPU as the CPU utilization estimate (see the *Per-entity load tracking*
435 utilization metric, so in principle its decisions should not contradict the
|
| D | intel_pstate.rst | 108 ``intel_pstate`` registers utilization update callbacks with the CPU scheduler
148 In this mode ``intel_pstate`` registers utilization update callbacks with the
153 periodically updated by those utilization update callbacks too.
174 utilization metric used by it is based on numbers coming from feedback
176 current CPU utilization.
178 This algorithm is run by the driver's utilization update callback for the
213 utilization update callbacks with the CPU scheduler and the ``scaling_cur_freq``
468 driver's utilization update callback by the CPU scheduler for that CPU.
|
| /Linux-v5.4/drivers/s390/cio/ |
| D | cmf.c | 582 u64 utilization, elapsed_time; in __cmb_utilization() local
584 utilization = time_to_nsec(device_connect_time + in __cmb_utilization()
592 return elapsed_time ? (utilization / elapsed_time) : 0; in __cmb_utilization()
|
| /Linux-v5.4/Documentation/devicetree/bindings/dma/ |
| D | qcom_hidma_mgmt.txt | 8 share the same bandwidth. The bandwidth utilization can be partitioned
|
| /Linux-v5.4/init/ |
| D | Kconfig | 721 bool "Enable utilization clamping for RT/FAIR tasks"
724 This feature enables the scheduler to track the clamped utilization
728 utilization allowed for RUNNABLE tasks. The max utilization defines
729 the maximum frequency a task should use while the min utilization
732 Both min and max utilization clamp values are hints to the scheduler,
739 int "Number of supported utilization clamp buckets"
750 clamp buckets tracking 20% utilization each. A 25% boosted tasks will
942 This feature enables the scheduler to track the clamped utilization
951 When task group based utilization clamping is enabled, an eventually
1871 utilization of a direct-mapped memory-side-cache. See section
[all …]
|
| /Linux-v5.4/fs/proc/ |
| D | Kconfig | 88 Various /proc files exist to monitor process memory utilization:
|
| /Linux-v5.4/Documentation/vm/ |
| D | frontswap.rst | 96 utilization in various system configurations:
101 cycles used in compression/decompression for better memory utilization.
124 optimize RAM utilization. And when guest OS's are induced to surrender
|
| /Linux-v5.4/arch/arc/boot/dts/ |
| D | axs10x_mb.dtsi | 112 * Most probably "Hold Register" utilization is platform-
|
| /Linux-v5.4/Documentation/networking/device_drivers/neterion/ |
| D | s2io.txt | 131 bring down CPU utilization.
|
| /Linux-v5.4/Documentation/admin-guide/device-mapper/ |
| D | cache-policies.rst | 50 The smq policy (vs mq) offers the promise of less memory utilization,
|
