News: 0001506952

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Lazy Preemption Merged Along With Other Scheduler Improvements For Linux 6.13

([Linux Kernel] 3 Hours Ago Lazy Preemption)


All of the scheduler feature changes were merged today for the Linux 6.13 kernel, including the introduction of the lazy preemption model.

As noted a few weeks back [1]lazy preemption "PREEMPT_LAZY" was tracking for introduction in the Linux 6.13 cycle. Lazy preemption is described in the scheduler pull request as:

Add the "Lazy preemption" model (CONFIG_PREEMPT_LAZY=y), which optimizes fair-class preemption by delaying preemption requests to the tick boundary, while working as full preemption for RR/FIFO/DEADLINE classes.

Or the Kconfig description for CONFIG_PREEMPT_LAZY that sums it up a bit more elegantly:

This option provides a scheduler driven preemption model that is fundamentally similar to full preemption, but is less eager to preempt SCHED_NORMAL tasks in an attempt to reduce lock holder preemption and recover some of the performance gains seen from using Voluntary preemption.

This lazy preemption option is currently working on x86_64 and RISC-V systems.

The Linux 6.13 scheduler code also now ensures idle tasks are only initialized once, a fair scheduler optimization, optimizing the generic idle loop by dropping an unnecessary memory barrier, [2]improving cache locality for Restartable Sequences (RSEQ), and [3]prep changes for Proxy Execution .

The lazy preemption code plus other scheduler changes make for a pretty exciting pull for Linux 6.13. The full list of scheduler patches for those interested via the [4]Linux kernel mailing list .



[1] https://www.phoronix.com/news/Linux-6.13-Lazy-Preemption

[2] https://www.phoronix.com/news/RSEQ-Cache-Local-Speedup

[3] https://www.phoronix.com/news/Linux-6.13-Prep-For-Proxy-Exec

[4] https://lore.kernel.org/lkml/Zzt_or2E2KEypfbi@gmail.com/



mrg666

skeevy420

Mitch

mrg666

sophisticles

If a system is administered wisely,
its users will be content.
They enjoy hacking their code
and don't waste time implementing
labor-saving shell scripts.
Since they dearly love their accounts,
they aren't interested in other machines.
There may be telnet, rlogin, and ftp,
but these don't access any hosts.
There may be an arsenal of cracks and malware,
but nobody ever uses them.
People enjoy reading their mail,
take pleasure in being with their newsgroups,
spend weekends working at their terminals,
delight in the doings at the site.
And even though the next system is so close
that users can hear its key clicks and biff beeps,
they are content to die of old age
without ever having gone to see it.