Commit 18b2bd03 authored by Aboorva Devarajan's avatar Aboorva Devarajan Committed by Tejun Heo

sched_ext: Documentation: Remove mentions of scx_bpf_switch_all

Updated sched_ext doc to eliminate references to scx_bpf_switch_all,
which has been removed in recent sched_ext versions.
Signed-off-by: default avatarAboorva Devarajan <aboorvad@linux.ibm.com>
Signed-off-by: default avatarTejun Heo <tj@kernel.org>
parent b651d7c3
...@@ -48,13 +48,16 @@ sched_ext is used only when the BPF scheduler is loaded and running. ...@@ -48,13 +48,16 @@ sched_ext is used only when the BPF scheduler is loaded and running.
If a task explicitly sets its scheduling policy to ``SCHED_EXT``, it will be If a task explicitly sets its scheduling policy to ``SCHED_EXT``, it will be
treated as ``SCHED_NORMAL`` and scheduled by CFS until the BPF scheduler is treated as ``SCHED_NORMAL`` and scheduled by CFS until the BPF scheduler is
loaded. On load, such tasks will be switched to and scheduled by sched_ext. loaded.
The BPF scheduler can choose to schedule all normal and lower class tasks by When the BPF scheduler is loaded and ``SCX_OPS_SWITCH_PARTIAL`` is not set
calling ``scx_bpf_switch_all()`` from its ``init()`` operation. In this in ``ops->flags``, all ``SCHED_NORMAL``, ``SCHED_BATCH``, ``SCHED_IDLE``, and
case, all ``SCHED_NORMAL``, ``SCHED_BATCH``, ``SCHED_IDLE`` and ``SCHED_EXT`` tasks are scheduled by sched_ext.
``SCHED_EXT`` tasks are scheduled by sched_ext. In the example schedulers,
this mode can be selected with the ``-a`` option. However, when the BPF scheduler is loaded and ``SCX_OPS_SWITCH_PARTIAL`` is
set in ``ops->flags``, only tasks with the ``SCHED_EXT`` policy are scheduled
by sched_ext, while tasks with ``SCHED_NORMAL``, ``SCHED_BATCH`` and
``SCHED_IDLE`` policies are scheduled by CFS.
Terminating the sched_ext scheduler program, triggering :kbd:`SysRq-S`, or Terminating the sched_ext scheduler program, triggering :kbd:`SysRq-S`, or
detection of any internal error including stalled runnable tasks aborts the detection of any internal error including stalled runnable tasks aborts the
...@@ -109,7 +112,7 @@ Userspace can implement an arbitrary BPF scheduler by loading a set of BPF ...@@ -109,7 +112,7 @@ Userspace can implement an arbitrary BPF scheduler by loading a set of BPF
programs that implement ``struct sched_ext_ops``. The only mandatory field programs that implement ``struct sched_ext_ops``. The only mandatory field
is ``ops.name`` which must be a valid BPF object name. All operations are is ``ops.name`` which must be a valid BPF object name. All operations are
optional. The following modified excerpt is from optional. The following modified excerpt is from
``tools/sched/scx_simple.bpf.c`` showing a minimal global FIFO scheduler. ``tools/sched_ext/scx_simple.bpf.c`` showing a minimal global FIFO scheduler.
.. code-block:: c .. code-block:: c
...@@ -156,13 +159,12 @@ optional. The following modified excerpt is from ...@@ -156,13 +159,12 @@ optional. The following modified excerpt is from
scx_bpf_dispatch(p, SCX_DSQ_GLOBAL, SCX_SLICE_DFL, enq_flags); scx_bpf_dispatch(p, SCX_DSQ_GLOBAL, SCX_SLICE_DFL, enq_flags);
} }
s32 BPF_STRUCT_OPS(simple_init) s32 BPF_STRUCT_OPS_SLEEPABLE(simple_init)
{ {
/* /*
* All SCHED_OTHER, SCHED_IDLE, and SCHED_BATCH tasks should * By default, all SCHED_EXT, SCHED_OTHER, SCHED_IDLE, and
* use sched_ext. * SCHED_BATCH tasks should use sched_ext.
*/ */
scx_bpf_switch_all();
return 0; return 0;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment