Searched refs:utilization (Results 1 – 25 of 54) sorted by relevance
123
| /Linux-v4.19/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-v4.19/Documentation/scheduler/ |
| D | sched-nice-design.txt | 42 a CPU utilization, but because it causes too frequent (once per
48 right minimal granularity - and this translates to 5% CPU utilization.
51 terms of CPU utilization, we only got complaints about it (still) being
95 the new scheduler makes nice(1) have the same CPU utilization effect on
98 utilization "split" between them as running a nice -5 and a nice -4
|
| D | sched-deadline.txt | 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
334 The utilization of a real-time task is defined as the ratio between its
338 If the total utilization U=sum(WCET_i/P_i) is larger than M (with M equal
341 Note that total utilization is defined as the sum of the utilizations
[all …]
|
| /Linux-v4.19/drivers/devfreq/event/ |
| D | Kconfig | 11 (e.g., raw data, utilization, latency, bandwidth). The events
32 utilization of each module.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-driver-genwqe | 46 Used for performance and utilization measurements.
52 Used for performance and utilization measurements.
|
| D | sysfs-fs-f2fs | 44 Controls the FS utilization condition for the in-place-update
|
| /Linux-v4.19/drivers/cpufreq/ |
| D | Kconfig | 152 changes frequency based on the CPU utilization.
194 This governor makes decisions based on the utilization data provided
196 the utilization/capacity ratio coming from the scheduler. If the
197 utilization is frequency-invariant, the new frequency is also
200 frequency tipping point is at utilization/capacity equal to 80% in
|
| /Linux-v4.19/fs/f2fs/ |
| D | debug.c | 91 si->utilization = utilization(sbi); in update_general_status()
283 si->utilization, si->valid_count, si->discard_blks); in stat_show()
286 si->utilization, si->valid_count); in stat_show()
|
| /Linux-v4.19/Documentation/networking/ |
| D | mpls-sysctl.txt | 8 A dense utilization of the entries in the platform label table
|
| D | e1000e.txt | 61 load on the system and can lower CPU utilization under heavy load,
112 are in use simultaneously, the CPU utilization may increase non-
113 linearly. In order to limit the CPU utilization without impacting
123 be platform-specific. If CPU utilization is not a concern, use
|
| D | e1000.rst | 104 load on the system and can lower CPU utilization under heavy load,
168 are in use simultaneously, the CPU utilization may increase non-
169 linearly. In order to limit the CPU utilization without impacting
179 be platform-specific. If CPU utilization is not a concern, use
192 incoming packets, at the expense of increased system memory utilization.
|
| D | s2io.txt | 131 bring down CPU utilization.
|
| D | xfrm_device.txt | 15 can radically increase throughput and decrease CPU utilization. The XFRM
|
| D | i40e.txt | 52 utilization can be significantly reduced when under large Rx load. GRO is
|
| /Linux-v4.19/Documentation/scsi/ |
| D | g_NCR5380.txt | 13 allow targets to disconnect and thereby improve SCSI bus utilization.
|
| /Linux-v4.19/Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 39 the utilization of the system generally changes over time, that has to be done
153 That callback it expected to register per-CPU utilization update callbacks for
155 The utilization update callbacks will be invoked by the CPU scheduler on
157 scheduler tick or generally whenever the CPU utilization may change (from the
182 to register per-CPU utilization update callbacks for each policy. These
384 This governor uses CPU utilization data available from the CPU scheduler. It
394 invoking its utilization update callback for that CPU. If it is invoked by the
399 given CPU as the CPU utilization estimate (see the `Per-entity load tracking`_
431 utilization metric, so in principle its decisions should not contradict the
|
| D | intel_pstate.rst | 106 ``intel_pstate`` registers utilization update callbacks with the CPU scheduler
146 In this mode ``intel_pstate`` registers utilization update callbacks with the
151 periodically updated by those utilization update callbacks too.
172 utilization metric used by it is based on numbers coming from feedback
174 current CPU utilization.
176 This algorithm is run by the driver's utilization update callback for the
211 utilization update callbacks with the CPU scheduler and the ``scaling_cur_freq``
466 driver's utilization update callback by the CPU scheduler for that CPU.
|
| /Linux-v4.19/Documentation/ABI/stable/ |
| D | sysfs-devices-node | 57 utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.txt
|
| /Linux-v4.19/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-v4.19/Documentation/devicetree/bindings/dma/ |
| D | qcom_hidma_mgmt.txt | 8 share the same bandwidth. The bandwidth utilization can be partitioned
|
| /Linux-v4.19/fs/proc/ |
| D | Kconfig | 86 Various /proc files exist to monitor process memory utilization:
|
| /Linux-v4.19/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-v4.19/Documentation/device-mapper/ |
| D | cache-policies.txt | 49 The smq policy (vs mq) offers the promise of less memory utilization,
|
| /Linux-v4.19/arch/arc/boot/dts/ |
| D | axs10x_mb.dtsi | 115 * Most probably "Hold Register" utilization is platform-
|
| /Linux-v4.19/arch/microblaze/ |
| D | Kconfig | 249 overhead. However the utilization of memory will increase.
|
123
