Liquorix ships a deliberately "clean" kernel and hits the pause button on its scheduler tinkering
Liquorix maintainer Steven Barrett merged the security-hardened Linux 7.3.4 into a deliberately clean build and called it a "capstone," pausing months of scheduler experimentation.
Liquorix maintainer Steven Barrett released the 7.3-2 build on Tuesday, folding the latest security-hardened Linux 7.3.4 into the distro's familiar low-latency configuration and then, tellingly, stopping there. It is the second build in Liquorix's 7.3 track, the first landing just two days earlier. But this one is different by design.
Barrett is calling it a "capstone." Rather than shipping the usual pile of experimental scheduler patches, he has folded stable upstream fixes into Liquorix's tuning and let them rest. After months of near-daily scheduler experimentation known as "Project-C," the message from the maintainer's side is about as clear as it gets.
What just shipped
The changelog itself is two lines. "Merge v7.3.4." "Update version to 7.3.4-1." No experimental scheduler patches. No reverted branches. Just a clean merge onto a well-tuned base.
Keep in mind this is not a kernel you should dismiss as boring. Linux 7.3.4 landed on the exact same day, handed out by Greg Kroah-Hartman as a security-focused maintenance release. It folds in two Xen security advisories for virtual networking, an AMD Zen 5 TSA_FILL CPU mitigation, plus a cluster of AppArmor hardening and filesystem correctness fixes. In short, you inherit a hardened networking and virtualization stack layered on top of Liquorix's responsiveness tuning.
That "clean" tag is what makes this noteworthy, though, because if you watch the changelog over the preceding weeks, you get the full picture. July and August were dominated by Project-C scheduler work, with hundreds of sched/alt micro-optimizations. By September, builds were reverting patches that had regressed. Late October brought rapid-fire builds back to back. Then came November 8's clean baseline on 7.3.3, and Tuesday's update one point release later.
Community reaction has been blunt about the shift. This is, as one observer put it, a deliberately clean and well-tested capstone rather than a batch of experimental patches, arriving after what felt like a master's thesis in scheduler optimization. For users who were wary of the cadence, that is reassuring. The catch is that the next builds may simply resume the experimentation, so this clean streak is probably short-lived.
The honest verdict
Liquorix inherits whatever upstream offers, and Linux 7.3 was a big one. The release was described as a record, with 18,765 non-merge commits from 3,021 developers, 807 of them first-timers.
Several pieces land squarely in Liquorix's wheelhouse. New VRAM management for low-end GPUs, driven by Valve's Natalie Vock, lets games that overcommit video memory keep running instead of backing off. Btrfs picked up faster fsync times in some scenarios. Older Radeon GPUs can now recover from hangs by resetting just the GFX block rather than starting over. There is even a ZTE fix that cut a KSM lock's worst-case stall from 705 milliseconds down to under 2, alongside a Xiaomi change in zsmalloc that reportedly yielded gains of up to 1.83x on a Raspberry Pi 4B.
The kernel is only half the story. Liquorix's reputation lives in its configuration. A 7.3.x build stacks a 1,000 Hz scheduler tick against the roughly 250 to 300 Hz you get from stock, which means less lag between your mouse movement and the system actually responding. On top of that sits a fully preemptible kernel, preemptible tree-based RCU, Kyber or BFQ disk I/O, and TCP BBR3 for networking. Memory handling pulls in multi-generational LRU, background hugepage reclaim, and compressed swap.
The philosophical core is Zen Interactive Tuning, which shifts scheduling timeslices down from 4ms to 2ms, turns split-lock detection off, and lowers CPU-frequency thresholds so cores ramp faster. That all comes at the documented cost of higher power use and somewhat lower raw throughput.
Liquorix targets Debian, Ubuntu, Fedora, and Arch Linux, on AMD64 only. The quickest route is a one-line script that adds the repo and installs the kernel.
curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bash
There is one caveat repeated across every platform, though. Liquorix does not support Secure Boot out of the box, so you may need to disable it in your BIOS, and the stock kernel stays as a GRUB fallback. Barrett keeps advising people to back up and verify their hardware before switching boot entries. It is a sensible caution, and one you would be wise to take.
Who is this for? Gamers chasing consistent frame times, audio and video producers who need predictable low-latency performance, and desktop power users who care more about feel than batch throughput. It is a poor fit for servers, which want throughput and efficiency, and for battery-powered laptops, where the responsiveness tuning eats into battery life. Benchmarks show Liquorix winning on interactivity and frame-time consistency while sometimes losing on raw throughput. It is arguably a sports car rather than a freight truck, and that is the fair way to think about it.
As of Tuesday, Liquorix sits on Linux 7.3.4 in a deliberate stability mode. Upstream has already moved on, with Linux 7.4-rc2 tagged earlier this week. Whether Barrett resumes the scheduler tinkering in the next build remains to be seen. For now, the 7.3 line ends on a note of tested reliability rather than restless innovation. Y
Head here to the Liquorix website for more details.
