| /linux/kernel/sched/ |
| H A D | cpufreq_schedutil.c | 21 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/phy/apple/ |
| H A D | atc.c | 563 * @tunables: Firmware-provided tunable parameters 564 * @tunables.axi2af: AXI to AF interface tunables 565 * @tunables.common: Common tunables for all lanes 566 * @tunables.lane_usb3: USB3 lane-specific tunables 567 * @tunables.lane_dp: DisplayPort lane-specific tunables 568 * @tunables.lane_usb4: USB4 lane-specific tunables 579 * @res: Resources for memory-mapped registers, used to verify that tunables aren't out of bounds 602 } 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() [all …]
|
| /linux/Documentation/block/ |
| H A D | kyber-iosched.rst | 2 Kyber I/O scheduler tunables 5 The only two tunables for the Kyber scheduler are the target latencies for
|
| H A D | switching-sched.rst | 5 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 D | deadline-iosched.rst | 2 Deadline IO scheduler tunables 6 In particular, it will clarify the meaning of the exposed tunables that may be
|
| H A D | bfq-iosched.rst | 68 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/platform/x86/ |
| H A D | asus-armoury.h | 226 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 …]
|
| H A D | asus-armoury.c | 1010 /* Set up the min/max and defaults for ROG tunables */ 1035 /* Initialize AC power tunables */ in init_rog_tunables() 1081 /* Initialize DC power tunables */ in init_rog_tunables()
|
| /linux/tools/cgroup/ |
| H A D | memcg_slabinfo.py | 117 ' : tunables %4u %4u %4u' 177 ' : tunables <limit> <batchcount> <sharedfactor>'
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | cache-policies.rst | 34 The following tunables are accepted, but have no effect::
|
| H A D | cache.rst | 158 Policies will have different tunables, specific to each one, so we 295 Policies will have different tunables, specific to each one, so we
|
| /linux/include/linux/platform_data/x86/ |
| H A D | asus-wmi.h | 106 /* Tunables for AUS ROG laptops */
|
| /linux/tools/testing/selftests/net/forwarding/ |
| H A D | tsn_lib.sh | 10 # Tunables
|
| H A D | tc_taprio.sh | 35 # Tunables
|
| /linux/tools/testing/selftests/drivers/net/ocelot/ |
| H A D | psfp.sh | 20 # Tunables
|
| /linux/tools/thermal/tmon/ |
| H A D | tui.c | 275 const char DIAG_TITLE[] = "[ TUNABLES ]"; 293 /* list all the available tunables */ in show_dialogue()
|
| /linux/Documentation/driver-api/thermal/ |
| H A D | power_allocator.rst | 2 Power allocator governor tunables
|
| /linux/tools/testing/selftests/mm/ |
| H A D | ksm_tests.c | 845 ksft_exit_fail_msg("Cannot save default tunables\n"); in main() 852 ksft_exit_fail_msg("Cannot set up KSM tunables\n"); in main() 905 ksft_print_msg("Cannot restore default tunables\n"); in main()
|
| /linux/drivers/net/ethernet/natsemi/ |
| H A D | sonic.h | 272 * Some tunables for the buffer areas. Power of 2 is required
|
| /linux/Documentation/scheduler/ |
| H A D | sched-util-clamp.rst | 26 performance constraints. It consists of two tunables: 215 The rq has a bucket for each uclamp_id tunables: [UCLAMP_MIN, UCLAMP_MAX].
|
| /linux/net/sched/ |
| H A D | sch_cbs.c | 18 * There are four tunables to be considered:
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | flow_dissector_classification.c | 747 if (!ASSERT_OK(err, "configure net tunables")) in test_global_init()
|
| /linux/net/sunrpc/xprtrdma/ |
| H A D | transport.c | 64 * tunables
|
| /linux/drivers/net/wireless/broadcom/brcm80211/brcmsmac/ |
| H A D | dma.c | 261 /* tunables */ 591 /* save tunables */ in dma_attach()
|
| /linux/Documentation/core-api/ |
| H A D | workqueue.rst | 621 scheduler improvements may make most of these tunables unnecessary.
|