diff options
| author | Kir Kolyshkin <kolyshkin@gmail.com> | 2021-01-20 03:18:16 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2021-01-21 21:40:21 +0300 |
| commit | f1779d13edf3157d8636b45bd756f9439ebe7d85 (patch) | |
| tree | 079f7ea8cff9eefda4e6182f6f12106e3c4e8cf9 /Documentation/scheduler | |
| parent | 7ebc7dc87103652c552ecd973b9e7bf24ee7c7c2 (diff) | |
| download | linux-f1779d13edf3157d8636b45bd756f9439ebe7d85.tar.xz | |
docs/scheduler/sched-design-CFS: formatting fix
Fix the rendering of the paragraph. Before the fix, the first line is
rendered in bold (I'm not quite sure why) and is also separated from the
rest of the paragraph, which is rendered with an indent.
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Acked-by: Tejun Heo <tj@kernel.org>
Link: https://lore.kernel.org/r/20210120001824.385168-3-kolyshkin@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/scheduler')
| -rw-r--r-- | Documentation/scheduler/sched-design-CFS.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/scheduler/sched-design-CFS.rst b/Documentation/scheduler/sched-design-CFS.rst index a96c72651877..59b2d1fb4dc4 100644 --- a/Documentation/scheduler/sched-design-CFS.rst +++ b/Documentation/scheduler/sched-design-CFS.rst @@ -34,9 +34,9 @@ In CFS the virtual runtime is expressed and tracked via the per-task p->se.vruntime (nanosec-unit) value. This way, it's possible to accurately timestamp and measure the "expected CPU time" a task should have gotten. -[ small detail: on "ideal" hardware, at any time all tasks would have the same - p->se.vruntime value --- i.e., tasks would execute simultaneously and no task - would ever get "out of balance" from the "ideal" share of CPU time. ] + Small detail: on "ideal" hardware, at any time all tasks would have the same + p->se.vruntime value --- i.e., tasks would execute simultaneously and no task + would ever get "out of balance" from the "ideal" share of CPU time. CFS's task picking logic is based on this p->se.vruntime value and it is thus very simple: it always tries to run the task with the smallest p->se.vruntime |