| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.txt | 35 - throttle-cfgs: A sub-node which is a container of configuration for each
36 hardware throttle events. These events can be set as cooling devices.
37 * throttle events: Sub-nodes must be named as "light" or "heavy".
39 - nvidia,priority: Each throttles has its own throttle settings, so the
40 SW need to set priorities for various throttle, the HW arbiter can select
41 the final throttle settings.
51 level of pulse skippers, which used to throttle clock frequencies. It
57 It is the level of pulse skippers, which used to throttle clock
70 valid only for OCx throttle events.
79 - nvidia,throttle-period-us: Specifies the number of uSec for which
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra124-soctherm.yaml | 62 throttle-cfgs:
65 hardware throttle events. These events can be set as cooling devices.
66 Throttle event sub-nodes must be named as "light" or "heavy".
76 description: Each throttles has its own throttle settings, so the
77 SW need to set priorities for various throttle, the HW arbiter
78 can select the final throttle settings. Bigger value indicates
94 of pulse skippers, which used to throttle clock frequencies. It
110 level of pulse skippers, which used to throttle clock
125 # Tegra210 specific and valid only for OCx throttle events
145 nvidia,throttle-period-us:
[all …]
|
| /kernel/linux/linux-5.10/fs/hmdfs/ |
| D | client_writeback.h | 17 * HMDFS_FILE_WB_BYTES - per-file throttle threshold
18 * HMDFS_FS_WB_BYTES - per-fs throttle threshold
74 /* per-file throttle threshold */
77 /* per-fs throttle threshold */
80 /* ratio between background thresh and throttle thresh */
83 /* ratio between file and fs throttle thresh */
87 * Enable auto-thresh. If enabled, the background and throttle
94 /* bandwitdh adjusted filesystem throttle thresh */
96 /* bandwidth adjusted per-file throttle thresh */
101 /* reclaimable pages exceed throttle thresh */
|
| /kernel/linux/linux-6.6/fs/hmdfs/ |
| D | client_writeback.h | 17 * HMDFS_FILE_WB_BYTES - per-file throttle threshold
18 * HMDFS_FS_WB_BYTES - per-fs throttle threshold
74 /* per-file throttle threshold */
77 /* per-fs throttle threshold */
80 /* ratio between background thresh and throttle thresh */
83 /* ratio between file and fs throttle thresh */
87 * Enable auto-thresh. If enabled, the background and throttle
94 /* bandwitdh adjusted filesystem throttle thresh */
96 /* bandwidth adjusted per-file throttle thresh */
101 /* reclaimable pages exceed throttle thresh */
|
| /kernel/linux/linux-5.10/drivers/thermal/ |
| D | gov_step_wise.c | 38 enum thermal_trend trend, bool throttle) in get_target_state() argument
54 if (throttle) { in get_target_state()
68 if (throttle) { in get_target_state()
76 if (throttle) in get_target_state()
81 if (!throttle) in get_target_state()
84 if (!throttle) { in get_target_state()
93 if (!throttle) in get_target_state()
122 bool throttle = false; in thermal_zone_trip_update() local
136 throttle = true; in thermal_zone_trip_update()
140 dev_dbg(&tz->device, "Trip%d[type=%d,temp=%d]:trend=%d,throttle=%d\n", in thermal_zone_trip_update()
[all …]
|
| D | gov_fair_share.c | 65 * throttle state of the cooling devices associated with the given zone.
68 * P1. max_state: Maximum throttle state exposed by the cooling device.
73 * We do not want to throttle too much when we trip a lower temperature,
122 .throttle = fair_share_throttle,
|
| D | Kconfig | 188 idle injection. This will throttle the CPU by injecting
200 This will throttle the device by limiting the maximum allowed DVFS
239 thermal framework. cpufreq is used as the cooling device to throttle
251 cpufreq is used as the cooling device to throttle CPUs when the
272 cpufreq is used as the cooling device to throttle CPUs when the passive
303 cpufreq is used as the cooling device to throttle CPUs when the
337 trip point. Cpufreq is used as the cooling device and will throttle
|
| /kernel/linux/linux-6.6/drivers/thermal/ |
| D | gov_step_wise.c | 31 enum thermal_trend trend, bool throttle) in get_target_state() argument
47 if (throttle) { in get_target_state()
56 if (throttle) { in get_target_state()
87 bool throttle = false; in thermal_zone_trip_update() local
93 throttle = true; in thermal_zone_trip_update()
97 dev_dbg(&tz->device, "Trip%d[type=%d,temp=%d]:trend=%d,throttle=%d\n", in thermal_zone_trip_update()
98 trip_id, trip->type, trip->temperature, trend, throttle); in thermal_zone_trip_update()
105 instance->target = get_target_state(instance, trend, throttle); in thermal_zone_trip_update()
133 * Throttling Logic: This uses the trend of the thermal zone to throttle.
155 .throttle = step_wise_throttle,
|
| D | gov_fair_share.c | 55 * throttle state of the cooling devices associated with the given zone.
58 * P1. max_state: Maximum throttle state exposed by the cooling device.
63 * We do not want to throttle too much when we trip a lower temperature,
111 .throttle = fair_share_throttle,
|
| D | Kconfig | 202 idle injection. This will throttle the CPU by injecting
214 This will throttle the device by limiting the maximum allowed DVFS
253 thermal framework. cpufreq is used as the cooling device to throttle
265 cpufreq is used as the cooling device to throttle CPUs when the
286 cpufreq is used as the cooling device to throttle CPUs when the passive
317 cpufreq is used as the cooling device to throttle CPUs when the
351 trip point. Cpufreq is used as the cooling device and will throttle
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 37 echo "8:16 1048576" > /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device
49 Limits for writes can be put using blkio.throttle.write_bps_device file.
247 - blkio.throttle.read_bps_device
252 echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device
254 - blkio.throttle.write_bps_device
259 echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device
261 - blkio.throttle.read_iops_device
266 echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device
268 - blkio.throttle.write_iops_device
273 echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device
[all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 38 echo "8:16 1048576" > /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device
50 Limits for writes can be put using blkio.throttle.write_bps_device file.
252 blkio.throttle.read_bps_device
257 echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.read_bps_device
259 blkio.throttle.write_bps_device
264 echo "<major>:<minor> <rate_bytes_per_second>" > /cgrp/blkio.throttle.write_bps_device
266 blkio.throttle.read_iops_device
271 echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.read_iops_device
273 blkio.throttle.write_iops_device
278 echo "<major>:<minor> <rate_io_per_second>" > /cgrp/blkio.throttle.write_iops_device
[all …]
|
| /kernel/linux/linux-5.10/drivers/tty/serial/8250/ |
| D | 8250_aspeed_vuart.c | 41 * If we fill the tty flip buffers, we throttle the data ready interrupt
242 bool throttle) in __aspeed_vuart_set_throttle() argument
247 if (!throttle) in __aspeed_vuart_set_throttle()
251 static void aspeed_vuart_set_throttle(struct uart_port *port, bool throttle) in aspeed_vuart_set_throttle() argument
257 __aspeed_vuart_set_throttle(up, throttle); in aspeed_vuart_set_throttle()
287 * have throttle/unthrottle callbacks, we've seen that the VUART device can
289 * against the throttle threshold. This results in dropped characters before
290 * the throttle.
293 * throttle now and schedule an unthrottle for later, once the ldisc has had
316 /* throttle and schedule an unthrottle later */ in aspeed_vuart_handle_irq()
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | dm-kcopyd.h | 26 unsigned throttle; member
44 module_param_named(name, dm_kcopyd_throttle.throttle, uint, 0644); \
49 * throttle can be NULL if you don't want any throttling.
52 struct dm_kcopyd_client *dm_kcopyd_client_create(struct dm_kcopyd_throttle *throttle);
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | dm-kcopyd.h | 27 unsigned int throttle; member
45 module_param_named(name, dm_kcopyd_throttle.throttle, uint, 0644); \
50 * throttle can be NULL if you don't want any throttling.
53 struct dm_kcopyd_client *dm_kcopyd_client_create(struct dm_kcopyd_throttle *throttle);
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/amd/include/ |
| D | kgd_pp_interface.h | 477 /* Throttle status */
529 /* Throttle status */
588 /* Throttle status (ASIC dependent) */
650 /* Throttle status */
677 /* Throttle status (ASIC independent) */
726 /* Throttle status */
776 /* Throttle status */
826 /* Throttle status (ASIC dependent) */
834 /* Throttle status (ASIC independent) */
879 /* Throttle status (ASIC dependent) */
[all …]
|
| /kernel/linux/linux-6.6/drivers/tty/serial/8250/ |
| D | 8250_aspeed_vuart.c | 44 * If we fill the tty flip buffers, we throttle the data ready interrupt
274 bool throttle) in __aspeed_vuart_set_throttle() argument
282 if (!throttle) in __aspeed_vuart_set_throttle()
286 static void aspeed_vuart_set_throttle(struct uart_port *port, bool throttle) in aspeed_vuart_set_throttle() argument
292 __aspeed_vuart_set_throttle(up, throttle); in aspeed_vuart_set_throttle()
322 * have throttle/unthrottle callbacks, we've seen that the VUART device can
324 * against the throttle threshold. This results in dropped characters before
325 * the throttle.
328 * throttle now and schedule an unthrottle for later, once the ldisc has had
351 /* throttle and schedule an unthrottle later */ in aspeed_vuart_handle_irq()
[all …]
|
| /kernel/linux/linux-5.10/drivers/thermal/tegra/ |
| D | soctherm.c | 497 * throttrip_program() - Configures the hardware to throttle the
501 * @stc: pointer to the throttle need to be triggered
504 * Sets the thermal trip threshold and throttle event of the given sensor
506 * throttle.
755 * "THROTTLE" trip points , using "thermtrips", "critical" or "hot"
758 * After they have been configured, THERMTRIP or THROTTLE will take
768 * THROTTLE has been enabled successfully when a message similar to
770 * ""throttrip: will throttle when sensor group XXX reaches YYYYYY mC"
822 "throttrip: will throttle when %s reaches %d mC\n", in tegra_soctherm_set_hwtrips()
828 dev_info(dev, "throttrip: %s: missing throttle cdev\n", in tegra_soctherm_set_hwtrips()
[all …]
|
| /kernel/linux/linux-6.6/drivers/thermal/tegra/ |
| D | soctherm.c | 497 * throttrip_program() - Configures the hardware to throttle the
501 * @stc: pointer to the throttle need to be triggered
504 * Sets the thermal trip threshold and throttle event of the given sensor
506 * throttle.
717 * "THROTTLE" trip points , using "thermtrips", "critical" or "hot"
720 * After they have been configured, THERMTRIP or THROTTLE will take
730 * THROTTLE has been enabled successfully when a message similar to
732 * ""throttrip: will throttle when sensor group XXX reaches YYYYYY mC"
784 "throttrip: will throttle when %s reaches %d mC\n", in tegra_soctherm_set_hwtrips()
790 dev_info(dev, "throttrip: %s: missing throttle cdev\n", in tegra_soctherm_set_hwtrips()
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-driver-intel-i915-hwmon | 15 The power controller will throttle the operating frequency
47 for client products. The power controller will throttle the
60 exposed for server products. The power controller will throttle
|
| /kernel/linux/linux-5.10/drivers/md/ |
| D | dm-kcopyd.c | 72 struct dm_kcopyd_throttle *throttle; member
122 unsigned throttle, now, difference; in io_job_start() local
131 throttle = READ_ONCE(t->throttle); in io_job_start()
133 if (likely(throttle >= 100)) in io_job_start()
155 skew = t->io_period - throttle * t->total_period / 100; in io_job_start()
181 if (likely(READ_ONCE(t->throttle) >= 100)) in io_job_finish()
520 io_job_finish(kc->throttle); in complete_io()
574 io_job_start(job->kc->throttle); in run_io_job()
909 struct dm_kcopyd_client *dm_kcopyd_client_create(struct dm_kcopyd_throttle *throttle) in dm_kcopyd_client_create() argument
924 kc->throttle = throttle; in dm_kcopyd_client_create()
|
| /kernel/linux/linux-6.6/drivers/md/ |
| D | dm-kcopyd.c | 75 struct dm_kcopyd_throttle *throttle; member
125 unsigned int throttle, now, difference; in io_job_start() local
134 throttle = READ_ONCE(t->throttle); in io_job_start()
136 if (likely(throttle >= 100)) in io_job_start()
159 skew = t->io_period - throttle * t->total_period / 100; in io_job_start()
185 if (likely(READ_ONCE(t->throttle) >= 100)) in io_job_finish()
525 io_job_finish(kc->throttle); in complete_io()
578 io_job_start(job->kc->throttle); in run_io_job()
915 struct dm_kcopyd_client *dm_kcopyd_client_create(struct dm_kcopyd_throttle *throttle) in dm_kcopyd_client_create() argument
930 kc->throttle = throttle; in dm_kcopyd_client_create()
|
| /kernel/linux/linux-5.10/block/ |
| D | blk-iolatency.c | 9 * - We will throttle all IO that comes in here if we need to.
15 * throttle time do we pay attention to the actual queue depth.
32 * an average latency of 5ms. If it does then we will throttle the "slow"
34 * throttle "unloved", but nobody else.
41 * There are 2 ways we throttle IO.
43 * 1) Queue depth throttling. As we throttle down we will adjust the maximum
46 * only way we throttle.
57 * and then at throttle time will do
61 * This induced delay will throttle back the activity that is generating the
352 * dig out of it. Just enough that we don't throttle/unthrottle in scale_cookie_change()
[all …]
|
| /kernel/linux/linux-5.10/drivers/tty/ |
| D | tty_ioctl.c | 105 * Takes the termios rwsem to protect against parallel throttle/unthrottle
115 tty->ops->throttle) in tty_throttle()
116 tty->ops->throttle(tty); in tty_throttle()
127 * Takes the termios rwsem to protect against parallel throttle/unthrottle
131 * Drivers should however remember that the stack can issue a throttle,
150 * Similar to tty_throttle() but will only attempt throttle
152 * throttle due to race conditions when throttling is conditional
168 if (tty->ops->throttle) in tty_throttle_safe()
169 tty->ops->throttle(tty); in tty_throttle_safe()
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/jaketown/ |
| D | uncore-memory.json | 232 "BriefDescription": "Critical Throttle Cycles",
248 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
257 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
266 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
275 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
284 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
293 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
302 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
311 "BriefDescription": "Throttle Cycles for Rank 0; DIMM ID",
|