1
0
Fork 0
Commit graph

3 commits

Author SHA1 Message Date
fe5e54c6d7 fix: remove incorrect kconfig path for scx_lavd
Some checks failed
/ Build onc-kde:main (push) Failing after 14m31s
/ Build onc-kde:main-ver4a (push) Has been skipped
/ Build onc-kde:main-nvidia (push) Has been skipped
/ Build onc-kde:main-nvidia-ver4a (push) Has been skipped
2026-01-25 19:14:02 +01:00
1c021f47d8 fix: add correct path to kconfig for scx_lavd
Some checks failed
/ Build onc-kde:main (push) Failing after 9m1s
/ Build onc-kde:main-ver4a (push) Has been skipped
/ Build onc-kde:main-nvidia (push) Has been skipped
/ Build onc-kde:main-nvidia-ver4a (push) Has been skipped
2026-01-25 17:28:25 +01:00
cadbd05c4a feat: add scx_lavd scheduler
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
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