JakeHillion/scx
1
0
Fork 0
mirror of https://github.com/JakeHillion/scx.git synced 2024-11-29 20:50:22 +00:00
Code Issues Packages Projects Releases Wiki Activity
d42bae4fcf
scx/scheds/rust
History
David Vernet d42bae4fcf
rusty: Print build ID when rusty is loaded 
When someone is testing schedulers, we often have to ask what version
the scheduler is running as. Now that we can access the build ID from
rust schedulers, let's update scx_rusty to print the build ID when rusty
first starts running.

This results in output such as the following:

```
[void@maniforge scx]$ rusty
19:04:26 [INFO] Running scx_rusty (build ID: 0.8.1-g2043d2537f37c8d75753bb65eb75bca965067564 x86_64-unknown-linux-gnu/debug)
19:04:26 [INFO] NUMA[00] mask= 0b11111111111111111111111111111111
19:04:26 [INFO]   DOM[00] mask= 0b00000000111111110000000011111111
19:04:26 [INFO]   DOM[01] mask= 0b11111111000000001111111100000000
19:04:26 [INFO] Rusty scheduler started!
```

Signed-off-by: David Vernet <void@manifault.com>
2024-06-25 11:44:46 -05:00
..
scx_lavd scx_lavd: revising tunables to reduce micro-stutters 2024-06-25 16:13:32 +09:00
scx_layered compat: Drop __COMPAT_scx_bpf_cpuperf_*() 2024-06-16 06:16:53 -10:00
scx_mitosis compat: Drop __COMPAT_scx_bpf_switch_all() 2024-06-15 20:03:37 -10:00
scx_rlfifo rlfifo: Use topo.nr_cpu_ids() instead of topo.nr_cpus_possible() 2024-06-21 12:57:20 -05:00
scx_rustland topo: Return nr_cpu_ids from host Topology 2024-06-21 12:57:13 -05:00
scx_rusty rusty: Print build ID when rusty is loaded 2024-06-25 11:44:46 -05:00
meson.build scheds: Add scx_mitosis scheduler 2024-06-11 10:34:53 -07:00
README.md scx_lavd: add scx_lavd (Latency-criticality Aware Virtual Deadline) scheduler 2024-03-16 10:31:07 +09:00

README.md

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