Home
last modified time | relevance | path

Searched refs:tunables (Results 1 – 13 of 13) sorted by relevance

/linux/kernel/sched/
H A Dcpufreq_schedutil.c21 struct sugov_tunables *tunables; member
73 (s64)sg_policy->tunables->rate_limit_us * NSEC_PER_USEC; in sugov_update_rate_limit_us()
604 struct sugov_tunables *tunables = to_sugov_tunables(attr_set); in rate_limit_us_show() local
606 return sysfs_emit(buf, "%u\n", tunables->rate_limit_us); in rate_limit_us_show()
612 struct sugov_tunables *tunables = to_sugov_tunables(attr_set); in rate_limit_us_store() local
619 tunables->rate_limit_us = rate_limit_us; in rate_limit_us_store()
738 struct sugov_tunables *tunables; in sugov_tunables_alloc() local
740 tunables = kzalloc_obj(*tunables); in sugov_tunables_alloc()
741 if (tunables) { in sugov_tunables_alloc()
742 gov_attr_set_init(&tunables->attr_set, &sg_policy->tunables_hook); in sugov_tunables_alloc()
[all …]
/linux/drivers/platform/x86/
H A Dasus-armoury.h226 struct rog_tunables *tunables = get_current_tunables(); \
228 if (!tunables || !tunables->power_limits) \
231 return sysfs_emit(buf, "%d\n", tunables->power_limits->_val); \
240 struct rog_tunables *tunables = get_current_tunables(); \
242 if (!tunables || !tunables->power_limits) \
247 tunables->power_limits->_attrname##_def ? \
248 tunables->power_limits->_attrname##_def : \
249 tunables->power_limits->_attrname##_max); \
259 struct rog_tunables *tunables = get_current_tunables(); \
261 if (!tunables || !tunables->power_limits) \
[all …]
/linux/Documentation/block/
H A Dkyber-iosched.rst2 Kyber I/O scheduler tunables
5 The only two tunables for the Kyber scheduler are the target latencies for
H A Dswitching-sched.rst5 Each io queue has a set of io scheduler tunables associated with it. These
6 tunables control how the io scheduler works. You can find these entries
H A Ddeadline-iosched.rst2 Deadline IO scheduler tunables
6 In particular, it will clarify the meaning of the exposed tunables that may be
H A Dbfq-iosched.rst68 3. What are BFQ's tunables and how to properly configure BFQ?
296 3. What are BFQ's tunables and how to properly configure BFQ?
299 Most BFQ tunables affect service guarantees (basically latency and
309 In particular, the tunables back_seek-max, back_seek_penalty,
/linux/drivers/phy/apple/
H A Datc.c602 } tunables; member
882 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.common[0]); in atcphy_apply_tunables()
883 apple_tunable_apply(atcphy->regs.axi2af, atcphy->tunables.axi2af); in atcphy_apply_tunables()
884 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.common[1]); in atcphy_apply_tunables()
894 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.lane_usb3[lane0]); in atcphy_apply_tunables()
895 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.lane_dp[lane1]); in atcphy_apply_tunables()
899 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.lane_dp[lane0]); in atcphy_apply_tunables()
900 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.lane_dp[lane1]); in atcphy_apply_tunables()
910 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.lane_usb4[lane0]); in atcphy_apply_tunables()
911 apple_tunable_apply(atcphy->regs.core, atcphy->tunables.lane_usb4[lane1]); in atcphy_apply_tunables()
[all …]
/linux/Documentation/admin-guide/device-mapper/
H A Dcache-policies.rst34 The following tunables are accepted, but have no effect::
H A Dcache.rst158 Policies will have different tunables, specific to each one, so we
295 Policies will have different tunables, specific to each one, so we
/linux/Documentation/driver-api/thermal/
H A Dpower_allocator.rst2 Power allocator governor tunables
/linux/Documentation/scheduler/
H A Dsched-util-clamp.rst26 performance constraints. It consists of two tunables:
215 The rq has a bucket for each uclamp_id tunables: [UCLAMP_MIN, UCLAMP_MAX].
/linux/Documentation/core-api/
H A Dworkqueue.rst621 scheduler improvements may make most of these tunables unnecessary.
/linux/net/netfilter/
H A DKconfig108 by means of per-address-family sysctl tunables.