Lines Matching +full:full +full:- +full:custom
6 programs - the BPF scheduler.
8 * sched_ext exports a full scheduling interface so that any scheduling
19 :kbd:`SysRq-S`.
24 `sched_ext_dump` tracepoint. The SysRq key sequence :kbd:`SysRq-D`
35 .. code-block:: none
54 in ``ops->flags``, all ``SCHED_NORMAL``, ``SCHED_BATCH``, ``SCHED_IDLE``, and
58 set in ``ops->flags``, only tasks with the ``SCHED_EXT`` policy are scheduled
62 Terminating the sched_ext scheduler program, triggering :kbd:`SysRq-S`, or
66 .. code-block:: none
68 # make -j16 -C tools/sched_ext
79 .. code-block:: none
90 .. code-block:: none
98 .. code-block:: none
113 .. code-block:: none
127 .. code-block:: c
183 exit_type = ei->type;
196 ---------------
206 DSQ. A non-local DSQ is "consumed" to transfer a task to the consuming CPU's
215 ----------------
228 A side-effect of selecting a CPU is waking it up from idle. While a BPF
250 * Immediately dispatch the task to a custom DSQ by calling
261 be used - ``SCX_DSQ_LOCAL``, ``SCX_DSQ_LOCAL_ON | cpu``,
262 ``SCX_DSQ_GLOBAL`` or a custom DSQ. While ``scx_bpf_dispatch()``
268 * ``scx_bpf_consume()`` tranfers a task from the specified non-local DSQ
287 built-in DSQs are used, there is no need to implement ``ops.dispatch()`` as
293 ``SCX_DSQ_LOCAL`` and ``SCX_DSQ_GLOBAL`` do not support priority-queue
311 custom DSQ.
313 * ``scx_qmap[.bpf].c``: A multi-level FIFO scheduler supporting five