/linux/Documentation/scheduler/ |
A D | sched-capacity.rst | 126 2. Task utilization 178 task utilization of 25%. 183 CPU capacity has a similar effect on task utilization in that running an 210 The task utilization signal can be made CPU invariant using the following 217 invariant task utilization of 25%. 219 2.4 Invariant task utilization 222 Both frequency and CPU invariance need to be applied to task utilization in 224 utilization that is both CPU and frequency invariant is thus, for a given 235 Any mention of task utilization in the following sections will imply its 241 Without a crystal ball, task behaviour (and thus task utilization) cannot [all …]
|
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 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 275 mechanism called 'over-utilization'. 278 5. Over-utilization 395 of CPUs follow their utilization. 400 least _requests_ frequencies calculated using the utilization signals. [all …]
|
A D | sched-deadline.rst | 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 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 347 Note that total utilization is defined as the sum of the utilizations 353 If, instead, the total utilization is smaller than M, then non real-time 366 utilization[12]. 375 of all the tasks executing on a CPU if and only if the total utilization [all …]
|
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
|
A D | schedutil.txt | 86 - Documentation/scheduler/sched-capacity.rst:"1. CPU Capacity + 2. Task utilization" 93 though when running their expected utilization will be the same, they suffer a 125 the frequency invariant utilization estimate of the CPU. From this we compute 159 will closely reflect utilization.
|
/linux/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/ |
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/drivers/devfreq/event/ |
A D | Kconfig | 12 (e.g., raw data, utilization, latency, bandwidth). The events 33 utilization of each module.
|
/linux/Documentation/ABI/testing/ |
A D | sysfs-driver-genwqe | 50 Used for performance and utilization measurements. 56 Used for performance and utilization measurements.
|
A D | sysfs-class-devfreq | 123 monitor the device status such as utilization. The user
|
/linux/drivers/cpufreq/ |
A D | Kconfig | 152 changes frequency based on the CPU utilization. 196 This governor makes decisions based on the utilization data provided 198 the utilization/capacity ratio coming from the scheduler. If the 199 utilization is frequency-invariant, the new frequency is also 202 frequency tipping point is at utilization/capacity equal to 80% in
|
/linux/Documentation/networking/device_drivers/ethernet/intel/ |
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
|
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.
|
A D | fm10k.rst | 93 utilization can be significantly reduced when under large Rx load. GRO is an
|
/linux/fs/f2fs/ |
A D | debug.c | 145 si->utilization = utilization(sbi); in update_general_status() 374 si->utilization, si->valid_count, si->discard_blks); in stat_show() 377 si->utilization, si->valid_count); in stat_show()
|
/linux/Documentation/networking/ |
A D | mpls-sysctl.rst | 15 A dense utilization of the entries in the platform label table
|
A D | mptcp-sysctl.rst | 54 an high value maximize links utilization on edge scenarios e.g. lossy
|
/linux/Documentation/admin-guide/pm/ |
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 387 This governor uses CPU utilization data available from the CPU scheduler. It 397 invoking its utilization update callback for that CPU. If it is invoked by the 402 given CPU as the CPU utilization estimate (see the *Per-entity load tracking* 434 utilization metric, so in principle its decisions should not contradict the
|
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/Documentation/scsi/ |
A D | g_NCR5380.rst | 19 allow targets to disconnect and thereby improve SCSI bus utilization.
|
/linux/drivers/s390/cio/ |
A D | cmf.c | 583 u64 utilization, elapsed_time; in __cmb_utilization() local 585 utilization = time_to_nsec(device_connect_time + in __cmb_utilization() 593 return elapsed_time ? (utilization / elapsed_time) : 0; in __cmb_utilization()
|
/linux/Documentation/devicetree/bindings/dma/ |
A D | qcom_hidma_mgmt.txt | 8 share the same bandwidth. The bandwidth utilization can be partitioned
|
/linux/Documentation/vm/ |
A 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/init/ |
A D | Kconfig | 818 bool "Enable utilization clamping for RT/FAIR tasks" 821 This feature enables the scheduler to track the clamped utilization 825 utilization allowed for RUNNABLE tasks. The max utilization defines 826 the maximum frequency a task should use while the min utilization 829 Both min and max utilization clamp values are hints to the scheduler, 836 int "Number of supported utilization clamp buckets" 1032 This feature enables the scheduler to track the clamped utilization 1041 When task group based utilization clamping is enabled, an eventually 1971 utilization of a direct-mapped memory-side-cache. See section 1978 10th order of pages is selected based on cache utilization [all …]
|
/linux/fs/proc/ |
A D | Kconfig | 88 Various /proc files exist to monitor process memory utilization:
|
/linux/include/uapi/misc/ |
A D | habanalabs.h | 445 __u32 utilization; member
|