Home
last modified time | relevance | path

Searched refs:vruntime (Results 1 – 10 of 10) sorted by relevance

/linux-6.15/Documentation/translations/zh_CN/scheduler/
H A Dsched-design-CFS.rst36 在CFS中，虚拟运行时间由每个任务的p->se.vruntime（单位为纳秒）的值表达和跟踪。因此，
39 一些细节：在“理想的”硬件上，所有的任务在任何时刻都应该具有一样的p->se.vruntime值，
42 CFS的任务选择逻辑基于p->se.vruntime的值，因此非常简单：总是试图选择p->se.vruntime值
64 CFS维护了一个按时间排序的红黑树，所有可运行任务以p->se.vruntime为键值排序。CFS从这颗
70 p->se.vruntime。一旦p->se.vruntime变得足够大，其它的任务将成为按时间排序的红黑树的
/linux-6.15/Documentation/scheduler/
H A Dsched-design-CFS.rst38 p->se.vruntime (nanosec-unit) value. This way, it's possible to accurately
42 p->se.vruntime value --- i.e., tasks would execute simultaneously and no task
45 CFS's task picking logic is based on this p->se.vruntime value and it is thus
46 very simple: it always tries to run the task with the smallest p->se.vruntime
66 increasing value tracking the smallest vruntime among all tasks in the
76 p->se.vruntime key. CFS picks the "leftmost" task from this tree and sticks to it.
85 p->se.vruntime. Once p->se.vruntime gets high enough so that another task
/linux-6.15/Documentation/translations/sp_SP/scheduler/
H A Dsched-design-CFS.rst45 cada tarea, en su valor de p->se.vruntime (en unidades de nanosegundos).
50 tareas pueden tener el mismo valor de p->se.vruntime --- i.e., tareas
54 La lógica de elección del tareas de CFS se basa en el valor de p->se.vruntime
56 p->se.vruntime más pequeño (i.e., la tarea que se ha ejecutado menos hasta el
78 monotónicamente siguiendo el valor más pequeño de vruntime de entre todas
90 p->se.vruntime. CFS selecciona la tarea más hacia la izquierda de este
100 p->se.vruntime. Una vez p->se.vruntime ha aumentado lo suficiente como
/linux-6.15/kernel/sched/
H A Dfair.c533 max_vruntime = vruntime; in max_vruntime()
542 min_vruntime = vruntime; in min_vruntime()
754 min_vruntime = vruntime; in __update_min_vruntime()
767 vruntime = curr->vruntime; in update_min_vruntime()
774 vruntime = se->min_vruntime; in update_min_vruntime()
776 vruntime = min_vruntime(vruntime, se->min_vruntime); in update_min_vruntime()
832 se->min_vruntime = se->vruntime; in min_vruntime_update()
853 se->min_vruntime = se->vruntime; in __enqueue_entity()
3796 se->deadline -= se->vruntime; in reweight_entity()
5286 se->vruntime = vruntime - lag; in place_entity()
[all …]
H A Ddebug.c669 PN(se->vruntime); in print_cfs_group_stats()
747 SPLIT_NS(p->se.vruntime), in print_task()
832 right_vruntime = last->vruntime; in print_cfs_rq()
1180 PN(se.vruntime); in proc_sched_show_task()
H A Dcore.c4486 p->se.vruntime = 0; in __sched_fork()
/linux-6.15/tools/perf/scripts/python/
H A Dsched-migration.py374 common_callchain, comm, pid, runtime, vruntime): argument
/linux-6.15/include/linux/
H A Dsched.h587 u64 vruntime; member
/linux-6.15/Documentation/timers/
H A Dno_hz.rst313 load, maintaining sched average, computing CFS entity vruntime,
/linux-6.15/Documentation/trace/
H A Dhistogram.rst2419 …941: sched_stat_runtime: comm=gnome-terminal- pid=1699 runtime=180706 [ns] vruntime=1126870572 [ns]
2424 … 309.874973: sched_stat_runtime: comm=rcu_sched pid=9 runtime=13646 [ns] vruntime=22531430286 [ns]
2520 …9.823113: sched_stat_runtime: comm=gnome-shell pid=1261 runtime=49347 [ns] vruntime=1835730389 [ns]
2523 …49.823118: sched_stat_runtime: comm=kworker/3:2 pid=135 runtime=5339 [ns] vruntime=17815800388 [ns]
2524 …49.823120: sched_stat_runtime: comm=kworker/6:2 pid=387 runtime=9594 [ns] vruntime=14589605367 [ns]