scx/scheds/rust/scx_lavd/meson.build

if serialize
  sched_deps = [libbpf, bpftool_target, sched]
else
  sched_deps = [libbpf, bpftool_target]
endif

sched = custom_target('scx_lavd',
              output: '@PLAINNAME@.__PHONY__',
              input: 'Cargo.toml',
              command: [cargo, 'build', '--manifest-path=@INPUT@', '--target-dir=@OUTDIR@',
                        cargo_build_args],
              env: cargo_env,
              depends: sched_deps,
              build_always_stale: true)
meson: introduce serialize build option With commit 5d20f89a ("scheds-rust: build rust schedulers in sequence"), schedulers are now built serially one after the other to prevent meson and cargo from forking NxN parallel tasks. However, this change has made building a single scheduler much more cumbersome, due to the chain of dependencies. For example, building scx_rusty using the specific meson target would still result in all schedulers being built, because they all depend on each other. To address this issue, introduce the new meson build option `serialize=true\|false` (default is false). This option allows to disable the schedulers' build chain, restoring the old behavior. With this option enabled, it is now possible to build just a single scheduler, parallelizing the cargo build properly, without triggering the build of the others. Example: $ meson setup build -Dbuildtype=release -Dserialize=false $ meson compile -C build scx_rusty Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-28 08:42:04 +01:00			`if serialize`
			`sched_deps = [libbpf, bpftool_target, sched]`
			`else`
			`sched_deps = [libbpf, bpftool_target]`
			`endif`

scheds-rust: build rust schedulers in sequence 2024-04-23 01:06:27 +01:00			`sched = custom_target('scx_lavd',`
scx_lavd: add scx_lavd (Latency-criticality Aware Virtual Deadline) scheduler scx_lavd is a BPF scheduler that implements an LAVD (Latency-criticality Aware Virtual Deadline) scheduling algorithm. While LAVD is new and still evolving, its core ideas are 1) measuring how much a task is latency critical and 2) leveraging the task's latency-criticality information in making various scheduling decisions (e.g., task's deadline, time slice, etc.). As the name implies, LAVD is based on the foundation of deadline scheduling. This scheduler consists of the BPF part and the rust part. The BPF part makes all the scheduling decisions; the rust part loads the BPF code and conducts other chores (e.g., printing sampled scheduling decisions). 2024-03-16 01:31:07 +00:00			`output: '@PLAINNAME@.__PHONY__',`
			`input: 'Cargo.toml',`
			`command: [cargo, 'build', '--manifest-path=@INPUT@', '--target-dir=@OUTDIR@',`
			`cargo_build_args],`
			`env: cargo_env,`
meson: introduce serialize build option With commit 5d20f89a ("scheds-rust: build rust schedulers in sequence"), schedulers are now built serially one after the other to prevent meson and cargo from forking NxN parallel tasks. However, this change has made building a single scheduler much more cumbersome, due to the chain of dependencies. For example, building scx_rusty using the specific meson target would still result in all schedulers being built, because they all depend on each other. To address this issue, introduce the new meson build option `serialize=true\|false` (default is false). This option allows to disable the schedulers' build chain, restoring the old behavior. With this option enabled, it is now possible to build just a single scheduler, parallelizing the cargo build properly, without triggering the build of the others. Example: $ meson setup build -Dbuildtype=release -Dserialize=false $ meson compile -C build scx_rusty Signed-off-by: Andrea Righi <andrea.righi@canonical.com> 2024-06-28 08:42:04 +01:00			`depends: sched_deps,`
scheds-rust: build rust schedulers in sequence 2024-04-23 01:06:27 +01:00			`build_always_stale: true)`