| /Linux-v5.10/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 | 185 if (pr->flags.throttling) in acpi_processor_max_state()
186 max_state += (pr->throttling.state_count -1); in acpi_processor_max_state()
223 if (pr->flags.throttling) in processor_get_cur_state()
224 *cur_state += pr->throttling.state; in processor_get_cur_state()
250 if (pr->flags.throttling && pr->throttling.state) in processor_set_cur_state()
|
| D | acpi_processor.c | 340 pr->throttling.address = object.processor.pblk_address; in acpi_processor_get_info()
341 pr->throttling.duty_offset = acpi_gbl_FADT.duty_offset; in acpi_processor_get_info()
342 pr->throttling.duty_width = acpi_gbl_FADT.duty_width; in acpi_processor_get_info()
378 if (!zalloc_cpumask_var(&pr->throttling.shared_cpu_map, GFP_KERNEL)) { in acpi_processor_add()
434 free_cpumask_var(pr->throttling.shared_cpu_map); in acpi_processor_add()
486 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 | 281 by several flavors of cpufreq performance-state, thermal, throttling and
535 like aggressive processor idling, throttling, frequency and/or
|
| /Linux-v5.10/block/ |
| D | Kconfig | 95 bool "Block layer bio throttling support"
99 Block layer bio throttling support. It can be used to limit
107 bool "Block throttling .low limit interface support (EXPERIMENTAL)"
110 Add .low limit interface for block throttling. The low limit is a best
128 bool "Enable support for block device writeback throttling"
132 less impact on foreground operations. The throttling is done
140 Enabling this option enables the .latency interface for IO throttling.
142 the configured latency target, throttling anybody with a higher latency
159 bool "Multiqueue writeback throttling"
163 Enable writeback throttling by default on multiqueue devices.
|
| /Linux-v5.10/drivers/gpu/drm/etnaviv/ |
| D | Kconfig | 19 bool "enable ETNAVIV thermal throttling"
23 Compile in support for thermal throttling.
|
| /Linux-v5.10/Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.txt | 4 or interrupt-based thermal monitoring, CPU and GPU throttling based
48 It is the throttling depth of pulse skippers, it's the percentage
49 throttling.
52 indicates cpu clock throttling depth, and the depth can be programmed.
58 frequencies. It indicates gpu clock throttling depth and can be
59 programmed to any of the following values which represent a throttling
80 throttling is engaged after the OC event is deasserted. Default value
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-platform-dfl-fme | 135 threshold, hardware starts 50% or 90% throttling (see
144 threshold, hardware starts 100% throttling.
177 0 AP2 state (90% throttling)
178 1 AP1 state (50% throttling)
193 this threshold, hardware starts 50% throttling.
206 this threshold, hardware starts 90% throttling.
|
| D | sysfs-platform-dfl-port | 23 means different throttling level. When reading this file, it
|
| /Linux-v5.10/Documentation/networking/device_drivers/ethernet/aquantia/ |
| D | atlantic.rst | 411 aq_itr -Interrupt throttling mode
418 0 Disable interrupt throttling.
419 1 Enable interrupt throttling and use specified tx and rx rates.
420 0xFFFF Auto throttling mode. Driver will choose the best RX and TX
431 TX side throttling in microseconds. Adapter will setup maximum interrupt delay
441 RX side throttling in microseconds. Adapter will setup maximum interrupt delay
|
| /Linux-v5.10/include/acpi/ |
| D | processor.h | 207 u8 throttling:1; member
231 struct acpi_processor_throttling throttling; member
|
| /Linux-v5.10/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.10/arch/arm/boot/dts/ |
| D | rk3288-veyron-mickey.dts | 101 * Add some discrete steps to help throttling system deal
113 * - After 696 MHz we stop lowering voltage, so throttling
|
| /Linux-v5.10/Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 503 for cooling device throttling control represents.
751 throttling the cooling devices according to the policy configured.
753 and does actual throttling for other trip points i.e ACTIVE and PASSIVE.
754 The throttling policy is based on the configured platform data; if no
755 platform data is provided, this uses the step_wise throttling policy.
|
| D | intel_powerclamp.rst | 39 are used for CPU throttling.
|
| /Linux-v5.10/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.10/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.10/Documentation/block/ |
| D | queue-sysfs.rst | 244 If the device is registered for writeback throttling, then this file shows
246 window of time (see wb_window_usec), then the writeback throttling will start
|
| /Linux-v5.10/Documentation/filesystems/nfs/ |
| D | nfs41-server.rst | 26 "exactly once" semantics and better control and throttling of the
|
| /Linux-v5.10/Documentation/vm/ |
| D | zswap.rst | 29 throttling by the hypervisor. This allows more work to get done with less
|
| /Linux-v5.10/Documentation/hid/ |
| D | intel-ish-hid.rst | 215 (up to IPC MTU), thus allowing for interrupt throttling.
|
| /Linux-v5.10/drivers/scsi/arcmsr/ |
| D | arcmsr_hba.c | 2498 uint32_t flag_ccb, throttling = 0; in arcmsr_hbaC_postqueue_isr() local
2519 throttling++; in arcmsr_hbaC_postqueue_isr()
2520 if (throttling == ARCMSR_HBC_ISR_THROTTLING_LEVEL) { in arcmsr_hbaC_postqueue_isr()
2523 throttling = 0; in arcmsr_hbaC_postqueue_isr()
|
