Home
last modified time | relevance | path

Searched refs:uclamp (Results 1 – 8 of 8) sorted by relevance

/openbmc/linux/Documentation/scheduler/
H A Dsched-util-clamp.rst10 Utilization clamping, also known as util clamp or uclamp, is a scheduler
39 the uclamp values as performance points rather than utilization is a better
78 By making these uclamp performance requests, or rather hints, user space can
100 Both SCHED_NORMAL/OTHER and SCHED_FIFO/RR honour uclamp requests/hints.
102 In the SCHED_FIFO/RR case, uclamp gives the option to run RT tasks at any
110 when an RT task wakes up. This cost is unchanged by using uclamp. Uclamp only
114 See :ref:`section 3.4 <uclamp-default-values>` for default values and
137 affected by the uclamp settings of all the tasks enqueued on it. For example if
143 rq, uclamp must do some housekeeping at every enqueue/dequeue, which is the
154 uclamp value at rq level a lot easier.
[all …]
H A Dsched-capacity.rst347 Furthermore, uclamp lets userspace specify a minimum and a maximum utilization
356 above. On top of that, uclamp is used to clamp the task utilization values,
362 By using uclamp, userspace can e.g. allow a busy loop (100% utilization) to run
363 on any CPU by giving it a low uclamp.max value. Conversely, it can force a small
365 giving it a high uclamp.min value.
/openbmc/linux/Documentation/translations/zh_CN/scheduler/
H A Dsched-capacity.rst307 此外，uclamp允许用户空间指定任务的最小和最大利用率，要么以sched_setattr()的方式，要么以
308 cgroup接口的方式（参阅Documentation/admin-guide/cgroup-v2.rst）。如其名字所暗示，uclamp
314 CFS任务唤醒的CPU选择，遵循上面描述的算力适应性准则。在此之上，uclamp被用来限制任务利用率，
320 通过使用uclamp，举例来说，用户空间可以允许忙等待循环（100%使用率）在任意CPU上运行，只要给
321 它设置低的uclamp.max值。相反，uclamp能强制一个小的周期性任务（比如，10%利用率）在最高性能
322 的CPU上运行，只要给它设置高的uclamp.min值。
/openbmc/linux/kernel/sched/
H A Dcore.c500 * - uclamp_update_active() p->uclamp*
1353 * This knob allows admins to change the default behavior when uclamp is being
1369 * This static key is used to reduce the uclamp overhead in the fast path. It
1373 * This allows users to continue to enable uclamp in their kernel config with
1374 * minimum uclamp overhead in the fast path.
1376 * As soon as userspace modifies any of the uclamp knobs, the static key is
1377 * enabled, since we have an actual users that make use of uclamp
1382 * * A task modifying its uclamp value with sched_setattr().
1384 * * An admin modifying the cgroup cpu.uclamp.{min, max}
1445 struct uclamp_bucket *bucket = rq->uclamp[clamp_i in uclamp_rq_max_value()
[all...]
H A Dsched.h412 struct uclamp_se uclamp[UCLAMP_CNT]; member
993 struct uclamp_rq uclamp[UCLAMP_CNT] ____cacheline_aligned; member
3053 return READ_ONCE(rq->uclamp[clamp_id].value); in uclamp_rq_get()
3059 WRITE_ONCE(rq->uclamp[clamp_id].value, value); in uclamp_rq_set()
3130 max_util = READ_ONCE(rq->uclamp[UCLAMP_MAX].value); in uclamp_rq_is_capped()
/openbmc/linux/Documentation/admin-guide/sysctl/
H A Dkernel.rst1209 It means that any requested uclamp.min value cannot be greater than
1220 It means that any requested uclamp.max value cannot be greater than
1231 Uclamp achieves this by setting the requested uclamp.min of all RT tasks to
1235 This knob allows admins to change the default behavior when uclamp is being
1241 requested uclamp.min value via sched_setattr() syscall.
/openbmc/linux/include/linux/
H A Dsched.h822 struct uclamp_se uclamp[UCLAMP_CNT]; member
/openbmc/linux/Documentation/admin-guide/
H A Dcgroup-v2.rst1098 cpu.uclamp.min
1111 `cpu.uclamp.max`.
1113 cpu.uclamp.max