Home
last modified time | relevance | path

Searched refs:utilization (Results 1 – 25 of 59) sorted by relevance

123

/linux/Documentation/scheduler/
H A Dsched-capacity.rst127 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 Dsched-nice-design.rst46 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 Dschedutil.rst90 - 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 Dsched-util-clamp.rst22 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/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/
H A Dgk20a.c125 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 Dintel_uncore_frequency_scaling.rst136 The hardware monitors the average CPU utilization across all cores
146 If the average CPU utilization is below a user-defined threshold
151 Similarly in high load scenario where the CPU utilization goes above
155 immediately with CPU utilization spikes.
166 threshold. This attribute is in percentages of CPU utilization.
170 threshold. This attribute is in percentages of CPU utilization.
177 * when CPU utilization is less than 10%: sets uncore frequency to 800MHz
178 * when CPU utilization is higher than 95%: increases uncore frequency in
/linux/drivers/devfreq/event/
H A DKconfig12 (e.g., raw data, utilization, latency, bandwidth). The events
33 utilization of each module.
/linux/Documentation/ABI/testing/
H A Dsysfs-driver-genwqe50 Used for performance and utilization measurements.
56 Used for performance and utilization measurements.
H A Dsysfs-driver-intel_sdsi79 utilization metrics of On Demand enabled features. Mailbox
H A Dsysfs-class-devfreq126 monitor the device status such as utilization. The user
/linux/drivers/cpufreq/
H A DKconfig151 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 De1000e.rst54 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 De1000.rst106 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.
H A Dfm10k.rst93 utilization can be significantly reduced when under large Rx load. GRO is an
H A Didpf.rst97 For lower CPU utilization:
/linux/Documentation/translations/zh_CN/scheduler/
H A Dschedutil.rst89 …cumentation/translations/zh_CN/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utilization"
/linux/Documentation/networking/
H A Dmpls-sysctl.rst15 A dense utilization of the entries in the platform label table
/linux/Documentation/scsi/
H A Dg_NCR5380.rst19 allow targets to disconnect and thereby improve SCSI bus utilization.
/linux/drivers/s390/cio/
H A Dcmf.c582 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/Documentation/admin-guide/device-mapper/
H A Dcache-policies.rst50 The smq policy (vs mq) offers the promise of less memory utilization,
/linux/arch/arc/boot/dts/
H A Daxs10x_mb.dtsi114 * Most probably "Hold Register" utilization is platform-
/linux/arch/riscv/
H A DKconfig.errata116 non-standard PTE utilization on T-Head SoCs (XTheadMae).
/linux/init/
H A DKconfig876 bool "Enable utilization clamping for RT/FAIR tasks"
879 This feature enables the scheduler to track the clamped utilization
883 utilization allowed for RUNNABLE tasks. The max utilization defines
884 the maximum frequency a task should use while the min utilization
887 Both min and max utilization clamp values are hints to the scheduler,
894 int "Number of supported utilization clamp buckets"
905 clamp buckets tracking 20% utilization each. A 25% boosted tasks will
1189 This feature enables the scheduler to track the clamped utilization
1198 When task group based utilization clamping is enabled, an eventually
/linux/Documentation/admin-guide/perf/
H A Dhisi-pcie-pmu.rst6 bandwidth, latency, bus utilization and buffer occupancy data of PCIe.
/linux/Documentation/arch/x86/
H A Dsva.rst36 Machines (VM's). This allows better hardware utilization vs. hard
37 partitioning resources that could result in under utilization. In order to

123