| /Linux-v5.4/drivers/acpi/ |
| D | processor_throttling.c | 78 pthrottling = &(pr->throttling); in acpi_processor_update_tsd_coord()
100 pthrottling = &pr->throttling; in acpi_processor_update_tsd_coord()
124 match_pthrottling = &(match_pr->throttling); in acpi_processor_update_tsd_coord()
157 match_pthrottling = &(match_pr->throttling); in acpi_processor_update_tsd_coord()
184 pthrottling = &(pr->throttling); in acpi_processor_update_tsd_coord()
223 if (!pr->flags.throttling) { in acpi_processor_throttling_notifier()
229 p_throttling = &(pr->throttling); in acpi_processor_throttling_notifier()
317 if (throttling_limit >= pr->throttling.state_count) { in acpi_processor_tstate_has_changed()
322 current_state = pr->throttling.state; in acpi_processor_tstate_has_changed()
373 pr->flags.throttling = 0; in acpi_processor_reevaluate_tstate()
[all …]
|
| D | processor_thermal.c | 187 if (pr->flags.throttling) in acpi_processor_max_state()
188 max_state += (pr->throttling.state_count -1); in acpi_processor_max_state()
225 if (pr->flags.throttling) in processor_get_cur_state()
226 *cur_state += pr->throttling.state; in processor_get_cur_state()
252 if (pr->flags.throttling && pr->throttling.state) in processor_set_cur_state()
|
| D | acpi_processor.c | 341 pr->throttling.address = object.processor.pblk_address; in acpi_processor_get_info()
342 pr->throttling.duty_offset = acpi_gbl_FADT.duty_offset; in acpi_processor_get_info()
343 pr->throttling.duty_width = acpi_gbl_FADT.duty_width; in acpi_processor_get_info()
379 if (!zalloc_cpumask_var(&pr->throttling.shared_cpu_map, GFP_KERNEL)) { in acpi_processor_add()
435 free_cpumask_var(pr->throttling.shared_cpu_map); in acpi_processor_add()
487 free_cpumask_var(pr->throttling.shared_cpu_map); in acpi_processor_remove()
|
| D | processor_driver.c | 151 if (pr->flags.throttling) in acpi_pss_perf_init()
|
| D | Kconfig | 274 by several flavors of cpufreq performance-state, thermal, throttling and
590 like aggressive processor idling, throttling, frequency and/or
|
| /Linux-v5.4/block/ |
| D | Kconfig | 87 bool "Block layer bio throttling support"
90 Block layer bio throttling support. It can be used to limit
98 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
101 Add .low limit interface for block throttling. The low limit is a best
119 bool "Enable support for block device writeback throttling"
123 less impact on foreground operations. The throttling is done
131 Enabling this option enables the .latency interface for IO throttling.
133 the configured latency target, throttling anybody with a higher latency
149 bool "Multiqueue writeback throttling"
153 Enable writeback throttling by default on multiqueue devices.
|
| /Linux-v5.4/drivers/gpu/drm/etnaviv/ |
| D | Kconfig | 19 bool "enable ETNAVIV thermal throttling"
23 Compile in support for thermal throttling.
|
| /Linux-v5.4/Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.txt | 4 or interrupt-based thermal monitoring, CPU and GPU throttling based
47 It is the throttling depth of pulse skippers, it's the percentage
48 throttling.
51 indicates cpu clock throttling depth, and the depth can be programmed.
57 frequencies. It indicates gpu clock throttling depth and can be
58 programmed to any of the following values which represent a throttling
78 throttling is engaged after the OC event is deasserted. Default value
|
| /Linux-v5.4/Documentation/networking/device_drivers/aquantia/ |
| D | atlantic.txt | 332 aq_itr -Interrupt throttling mode
336 0 - Disable interrupt throttling.
337 1 - Enable interrupt throttling and use specified tx and rx rates.
338 0xFFFF - Auto throttling mode. Driver will choose the best RX and TX
345 TX side throttling in microseconds. Adapter will setup maximum interrupt delay
352 RX side throttling in microseconds. Adapter will setup maximum interrupt delay
|
| /Linux-v5.4/include/acpi/ |
| D | processor.h | 207 u8 throttling:1; member
231 struct acpi_processor_throttling throttling; member
|
| /Linux-v5.4/Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 13 One IO control policy is throttling policy which can be used to
26 - Enable throttling in block layer::
55 throttling's hierarchy support is enabled iff "sane_behavior" is
68 hierarchy correctly. For throttling, all limits apply
90 - Enable block device throttling support in block layer.
|
| /Linux-v5.4/arch/arm/boot/dts/ |
| D | rk3288-veyron-mickey.dts | 93 * Add some discrete steps to help throttling system deal
105 * - After 696 MHz we stop lowering voltage, so throttling
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-port | 23 means different throttling level. When reading this file, it
|
| /Linux-v5.4/Documentation/hwmon/ |
| D | jc42.rst | 110 systems use the sensor to prevent memory overheating by automatically throttling
|
| D | asc7621.rst | 205 throttling. This means that these are usually negative numbers.
|
| /Linux-v5.4/Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 503 for cooling device throttling control represents.
765 throttling the cooling devices according to the policy configured.
767 and does actual throttling for other trip points i.e ACTIVE and PASSIVE.
768 The throttling policy is based on the configured platform data; if no
769 platform data is provided, this uses the step_wise throttling policy.
|
| D | intel_powerclamp.rst | 39 are used for CPU throttling.
|
| /Linux-v5.4/Documentation/scheduler/ |
| D | sched-deadline.rst | 216 - Umax is the maximum reclaimable utilization (subjected to RT throttling
221 (subjected to RT throttling limits).
567 tasks with real-time group scheduling (a.k.a. RT-throttling - see
575 A main difference between deadline bandwidth management and RT-throttling
577 and thus we don't need a higher level throttling mechanism to enforce the
657 dl_yielded is set and used to handle correctly throttling and runtime
710 throttling patches [https://lkml.org/lkml/2010/2/23/239] but we still are in
|
| D | sched-bwc.rst | 30 cpu.stat: exports throttling statistics [explained further below]
|
| /Linux-v5.4/Documentation/block/ |
| D | queue-sysfs.rst | 222 If the device is registered for writeback throttling, then this file shows
224 window of time (see wb_window_usec), then the writeback throttling will start
|
| /Linux-v5.4/Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 24 "exactly once" semantics and better control and throttling of the
|
| /Linux-v5.4/Documentation/vm/ |
| D | zswap.rst | 29 throttling by the hypervisor. This allows more work to get done with less
|
| /Linux-v5.4/Documentation/hid/ |
| D | intel-ish-hid.rst | 215 (up to IPC MTU), thus allowing for interrupt throttling.
|
| /Linux-v5.4/drivers/scsi/arcmsr/ |
| D | arcmsr_hba.c | 2415 uint32_t flag_ccb, throttling = 0; in arcmsr_hbaC_postqueue_isr() local
2436 throttling++; in arcmsr_hbaC_postqueue_isr()
2437 if (throttling == ARCMSR_HBC_ISR_THROTTLING_LEVEL) { in arcmsr_hbaC_postqueue_isr()
2440 throttling = 0; in arcmsr_hbaC_postqueue_isr()
|
| /Linux-v5.4/drivers/thermal/ |
| D | Kconfig | 137 used for fans without throttling. Some fan drivers depend on this
|
