Debian 11112 Ubuntu 7267 Arch Linux 1044 Fedora Linux 9493 Published by

Liquorix maintainer Steven Barrett tagged the 7.3-7 kernel build on November 21, 2026, riding the newly stabilized Linux 7.3.5 stable base. This fixes-and-optimizations release leans heavily into memory management, adding swap accounting fixes, compressed-swap (zswap) cleanup, and a synced MGLRU-FG backport. It also delivers two defensive tweaks to the custom PDS scheduler and continues the project's ongoing Project-C tuning after a week of clean capstone builds. Aimed at gamers and audio/video producers who value low latency, it isn't suited for servers or battery-powered laptops.



Liquorix Releases 7.3-7 Kernel, Pivots Toward Memory and Swap Fixes

The enthusiast low-latency kernel leans back into tuning. Maintainer Steven Barrett tagged the 7.3-7 build Saturday, riding the freshly stabilized Linux 7.3.5 stable base with a batch of swap, compressed-swap, and scheduler fixes layered on top.

This is a fixes-and-optimizations release, not a bare baseline. The changelog leans hard into memory management.

Liquorix

The biggest chunk lands in swap handling. Barrett's mm/swap changes keep the memory-pressure window open across a whole batch of pages instead of re-evaluating state on every individual page-in. Less churn, less overhead when the system is actively swapping, which is exactly when interactive latency tends to suffer.

On top of that, synchronous swap reads now count as memory stalls. That lets the scheduler treat a task blocked on a swap read a bit more like one blocked on RAM. There's also a fix for large swap-ins spanning multiple swap file extents, plus a zswap tweak that drops a stale entry when it runs into a zero folio. Folios full of zeros shouldn't be compressed in the first place.

The custom PDS scheduler gets two smaller fixes.

One sets need_freq_update in ignore_dl_rate_limit() so frequency management stays responsive even on code paths that otherwise ignore the real-time rate limit. The second change is more mundane but sharper: it restores a missing mutex_unlock() on the cancel path of moving tasks in and out of a cpuset. Leave that out and you risk leaving a mutex held, with a deadlock a boot away.

Oh, and Liquorix synced its MGLRU-FG backport with version 5 of the upstream series. MGLRU is an advanced page-reclaim algorithm, and it's the same area that briefly folded into a gaming kernel earlier in the cycle.

Who should actually install this

Liquorix trades a little throughput and battery life for less scheduling jitter and smoother frame times. That's the pitch, and it mostly holds.

It's a good fit for gamers chasing consistent frame times, audio/video producers who need predictable low latency, and desktop power users who care about feel more than raw batch throughput.

Servers chasing efficiency don't want it. Battery-powered laptops shouldn't bother either, since the responsiveness tuning burns through charge faster. Hard real-time workloads are better served by a proper RT kernel.

Keep in mind a few constraints. The kernel is AMD64 only, deliberately, with no ARM builds. Secure Boot isn't supported out of the box, so expect to disable it in the BIOS. The stock distro kernel stays installed as a GRUB fallback, so a bad boot can usually be recovered by selecting the previous entry. On Fedora, Liquorix becomes and stays the default boot entry unless you set UPDATEDEFAULT=no in /etc/sysconfig/kernel.

Getting it

The one-line installer stays the same:

curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bash

The 7.3-7 packages are live in Liquorix's Debian pool right now, for bookworm, forky, sid, and trixie. There are also builds for Ubuntu, Fedora, and Arch.

Head here for the changelog and full release notes on GitHub.