Home
last modified time | relevance | path

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

/linux-6.3-rc2/Documentation/scheduler/
A Dsched-util-clamp.rst157 uclamp value of the rq. See :ref:`section 2.1 <uclamp-buckets>` for details on
249 rq->uclamp[UCLAMP_MIN] = max(rq->uclamp[UCLAMP_MIN], p->uclamp[UCLAMP_MIN])
309 uclamp settings.
376 * cpu.uclamp.min
377 * cpu.uclamp.max
420 p0->uclamp[UCLAMP_MIN] = cgroup0->cpu.uclamp.min = 20% * 1024;
421 p0->uclamp[UCLAMP_MAX] = cgroup0->cpu.uclamp.max = 60% * 1024;
430 p0->uclamp[UCLAMP_MIN] = cgroup1->cpu.uclamp.min = 60% * 1024;
431 p0->uclamp[UCLAMP_MAX] = cgroup1->cpu.uclamp.max = 100% * 1024;
433 p1->uclamp[UCLAMP_MIN] = cgroup1->cpu.uclamp.min = 60% * 1024;
[all …]
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.
/linux-6.3-rc2/Documentation/translations/zh_CN/scheduler/
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值。
/linux-6.3-rc2/kernel/sched/
A Dcore.c1505 if (p->uclamp[clamp_id].active) in uclamp_eff_value()
1526 struct uclamp_rq *uc_rq = &rq->uclamp[clamp_id]; in uclamp_rq_inc_id()
1527 struct uclamp_se *uc_se = &p->uclamp[clamp_id]; in uclamp_rq_inc_id()
1565 struct uclamp_se *uc_se = &p->uclamp[clamp_id]; in uclamp_rq_dec_id()
1674 if (!p->uclamp[clamp_id].active) in uclamp_rq_reinc_id()
1957 p->uclamp[clamp_id].active = false; in uclamp_fork()
1976 struct uclamp_rq *uc_rq = rq->uclamp; in init_uclamp_rq()
2007 root_task_group.uclamp[clamp_id] = uc_max; in init_uclamp()
10225 tg->uclamp[clamp_id] = parent->uclamp[clamp_id]; in alloc_uclamp_sched_group()
10495 ? css_tg(css)->parent->uclamp : NULL; in cpu_util_update_eff()
[all …]
A Dsched.h418 struct uclamp_se uclamp[UCLAMP_CNT]; member
988 struct uclamp_rq uclamp[UCLAMP_CNT] ____cacheline_aligned; member
3005 return READ_ONCE(rq->uclamp[clamp_id].value); in uclamp_rq_get()
3011 WRITE_ONCE(rq->uclamp[clamp_id].value, value); in uclamp_rq_set()
3082 max_util = READ_ONCE(rq->uclamp[UCLAMP_MAX].value); in uclamp_rq_is_capped()
/linux-6.3-rc2/Documentation/admin-guide/sysctl/
A Dkernel.rst1161 It means that any requested uclamp.min value cannot be greater than
1172 It means that any requested uclamp.max value cannot be greater than
1183 Uclamp achieves this by setting the requested uclamp.min of all RT tasks to
1187 This knob allows admins to change the default behavior when uclamp is being
1193 requested uclamp.min value via sched_setattr() syscall.
/linux-6.3-rc2/include/linux/
A Dsched.h813 struct uclamp_se uclamp[UCLAMP_CNT]; member
/linux-6.3-rc2/Documentation/admin-guide/
A Dcgroup-v2.rst1098 cpu.uclamp.min
1111 `cpu.uclamp.max`.
1113 cpu.uclamp.max

Completed in 48 milliseconds