1
0
Fork 0
ostree-native-containers/containers
ver4a cadbd05c4a
Some checks failed
/ Build onc-kde:main-ver4a (push) Has been cancelled
/ Build onc-kde:main (push) Has been cancelled
/ Build onc-kde:main-nvidia (push) Has been cancelled
/ Build onc-kde:main-nvidia-ver4a (push) Has been cancelled
feat: add scx_lavd scheduler
It seems to be the most energy efficient on my lunar lake laptop, having
the lowest low-utilization power draw
(scx_lavd intel_pstate active > intel pstate active > EAS intel pstate
passive), but there are some odd performance results, where only E-cores are used for
single-threaded workloads like "zstd -b1" and "pv /dev/urandom >
/dev/null". From my initial testing it seems to be way more convervative
with using P-cores for these specific workloads, and only uses them if
most of E-cores get overloaded, unlike EAS that engages P-cores when one
E-core is utilized above 80%.
2026-01-25 17:24:14 +01:00
..
etc feat: add scx_lavd scheduler 2026-01-25 17:24:14 +01:00
selinux-policies (ver4a) Add custom policy for ifconfig 2025-10-12 15:22:20 +02:00
usr/lib/bootc/kargs.d Enable root fs compression using rootflags 2025-08-09 23:50:37 +02:00
usr.nvidia/lib/bootc/kargs.d Optimize repository 2025-04-29 15:08:01 +02:00
Dockerfile.gnome (mpv) Add LittleCMS 2 2025-07-30 21:37:06 +02:00
Dockerfile.gnome-nvidia Optimize repository 2025-04-29 15:08:01 +02:00
Dockerfile.kde feat: add scx_lavd scheduler 2026-01-25 17:24:14 +01:00
Dockerfile.kde-nvidia Optimize repository 2025-04-29 15:08:01 +02:00
Dockerfile.kde-nvidia-ver4a Revert "feat: Stop removing plasma discover" 2026-01-19 00:42:55 +01:00
Dockerfile.kde-ver4a Revert "feat: Stop removing plasma discover" 2026-01-19 00:42:55 +01:00
mpv_options Optimize repository 2025-04-29 15:08:01 +02:00