4d98862674
Provide an interface for the BPF dispatcher and user-space scheduler to share CPU information. This information can empower the user-space scheduler to make more informed decisions and enable the implementation of a broader range of scheduling policies. With this change the BPF dispatcher provides a CPU map (one entry per CPU) that stores the pid that is running on each CPU (0 if the CPU is idle). The CPU map is updated by the BPF dispatcher in the .running() and .stopping() callbacks. The dispatcher then sends to the user-space scheduler a suggestion of the candidate CPU for each task that needs to run (that is always the previously used CPU), along with all the task's information. The user-space scheduler can decide to confirm the selected CPU or to choose a different one, using all the shared CPU information. Lastly, the selected CPU is communicated back to the dispatcher along with all the task's information and the BPF dispatcher takes care of executing the task on the selected CPU, eventually triggering a migration. Signed-off-by: Andrea Righi <andrea.righi@canonical.com> |
||
|---|---|---|
| .. | ||
| c | ||
| include | ||
| rust | ||
| meson.build | ||
| README.md | ||
| sync-to-kernel.sh | ||
SCHED_EXT SCHEDULERS
Introduction
This directory contains the repo's schedulers.
Some of these schedulers are simply examples of different types of schedulers that can be built using sched_ext. They can be loaded and used to schedule on your system, but their primary purpose is to illustrate how various features of sched_ext can be used.
Other schedulers are actually performant, production-ready schedulers. That is, for the correct workload and with the correct tuning, they may be deployed in a production environment with acceptable or possibly even improved performance. Some of the examples could be improved to become production schedulers.
Please see the following README files for details on each of the various types of schedulers:
- rust describes all of the schedulers with rust user space components. All of these schedulers are production ready.
- c describes all of the schedulers with C user space components. All of these schedulers are production ready.
Note on syncing
Note that there is a sync-to-kernel.sh script in this directory. This is used to sync any changes to the specific schedulers with the Linux kernel tree. If you've made any changes to a scheduler in please use the script to synchronize with the sched_ext Linux kernel tree:
$ ./sync-to-kernel.sh /path/to/kernel/tree