Hacker News Reader

I believe something like the mechanism you are describing has been in production at Google for at least a decade. See this talk [1].

The kernel interface that the article uses (called sched_ext) is the result of the attempts to mainstream the Google thing.

Yeah, I'm loosely familiar with sched_ext already. However, it is actually the opposite of scheduler activations.

SA means upcalling to user-space when thread scheduling is required.

sched_ext means loading a scheduler (coded in BPF) into the kernel.

Not dissimilar goals/purposes but wildly different systems.

Thanks for the clarification!