scx/scheds/rust
Andrea Righi 6d2aac1591 scx_rustland_core: introduce dispatch flags
Reserve some bits of the `cpu` attribute of a task to store special
dispatch flags.

Initially, let's introduce just RL_CPU_ANY to replace the special value
NO_CPU, indicating that the task can be dispatched on any CPU,
specifically the first CPU that becomes available.

This allows to keep the CPU value assigned by the builtin idle selection
logic, that can potentially be used later for further optimizations.

Moreover, having the possibility to specify dispatch flags gives more
flexibility and it allows to map new scheduling features to such flags.

Signed-off-by: Andrea Righi <andrea.righi@canonical.com>
2024-04-23 07:13:30 +02:00
..
scx_lavd scheds-rust: build rust schedulers in sequence 2024-04-23 08:06:27 +08:00
scx_layered scheds-rust: build rust schedulers in sequence 2024-04-23 08:06:27 +08:00
scx_rlfifo scheds-rust: build rust schedulers in sequence 2024-04-23 08:06:27 +08:00
scx_rustland scx_rustland_core: introduce dispatch flags 2024-04-23 07:13:30 +02:00
scx_rusty scheds-rust: build rust schedulers in sequence 2024-04-23 08:06:27 +08:00
meson.build scheds-rust: add explanation for chaining schedulers 2024-04-23 08:30:38 +08:00
README.md scx_lavd: add scx_lavd (Latency-criticality Aware Virtual Deadline) scheduler 2024-03-16 10:31:07 +09:00

RUST SCHEDULERS

Introduction

This directory contains schedulers with user space rust components.

The README in each scheduler directory provides some background and describes the types of workloads or scenarios they're designed to accommodate. For more details on any of these schedulers, please see the header comment in their main.rs or *.bpf.c files.

Schedulers