Linux 7.2 is now stable and arrives with a rather uncommon combination of improvements capable of affecting both personal computers and servers: a scheduler that considers shared CPU cache, significant changes to Btrfs and memory recovery, advances in virtualization, and a highly anticipated step forward for HDMI 2.1 FRL on AMD Radeon graphics. Linus Torvalds published the final version on August 16, 2026, after a particularly active development phase, with several fixes and reverted changes before closing the kernel.
The key points of Linux 7.2 in 30 seconds
- Linux 7.2 incorporates Cache Aware Scheduling, designed to keep certain threads sharing data within the same LLC (Last Level Cache) domain.
- Btrfs enables large pages by default and adds support for huge pages of up to 2 MiB, still with precautions.
- MGLRU receives updates to improve memory recovery and handling of dirty pages.
- AMDGPU implements the foundation for HDMI 2.1 FRL, though FreeSync and VRR over FRL are not fully completed yet.
- Moreover, there are new features for KVM, NFS, networking, Intel, IBM Z, and numerous device drivers.
At first glance, this may seem like another kernel release with change logs appealing mainly to driver developers. However, this time key components of the system are affected: how Linux schedules processes on cores, how it uses processor caches, how it moves data between memory and storage, and how it leverages modern video outputs.
That doesn’t necessarily mean upgrading to Linux 7.2 will automatically speed up every computer. Many improvements depend on hardware, workload type, and whether distributions adopt this version promptly. Still, the changes are significant enough that their impact could be felt from a home workstation to a high-core count server.
Linux starts to consider cache locality before moving processes
One of the most interesting innovations is Cache Aware Scheduling, mainly developed by Intel engineers to give the scheduler better information about the structure of the last level cache (LLC).
Modern processors do not have all cores sharing the cache equally. There may be multiple LLC domains within a single system, and moving a thread from one to another can lead to losing data already close to the processor.
Linux 7.2 introduces infrastructure to try to group threads sharing information within the same LLC domain. The aim is to reduce unnecessary migrations and increase the likelihood that required data remains in a nearby cache.
The code makes it clear, however, that not all workloads benefit from this strategy.
The system mainly targets multi-threaded applications with threads sharing data. Single-thread processes are usually excluded, as they gain little benefit, and tracking their cache residency adds overhead. Linux also avoids applying this policy aggressively to processes with too many threads or large memory footprints that could saturate an LLC.
The kernel even estimates the effective LLC size available as a reference before deploying a workload. If it determines that the process’s memory requirements exceed that capacity, it may decide not to group its threads.
In other words, this is not just an algorithm trying to fill the cache at all costs. Linux 7.2 introduces mechanisms to decide when it makes sense and when it could hurt performance.
This enhancement is especially relevant for modern AMD and Intel CPUs with multiple cache domains and many cores. Applications like databases, certain servers, or heavy multi-threaded workloads are more likely to benefit than typical single-thread desktop programs.
Btrfs moves more data at once; MGLRU improves memory pressure handling
Storage also sees significant work.
Btrfs enables support for large pages by default, an evolution of page management that allows working with larger memory units than the traditional 4 KiB pages in certain operations.
Additionally, the filesystem supports huge pages up to 2 MiB. It’s important to distinguish these concepts: large pages are now a regular part of Linux 7.2’s behavior, whereas support for huge pages of up to 2 MiB is still maturing and should be used cautiously as it’s not yet universally guaranteed.
These changes enable processing larger amounts of data with fewer internal operations and can reduce overhead in specific I/O scenarios.
There are tangible improvements. For example, Linux 7.2 reduces block operation sizes during writeback to prevent excessive accumulation, resulting in about a 15% improvement in sequential writes during tested scenarios. Another change removes unnecessary serialization of direct I/O after an API migration, achieving up to a 60% increase in throughput in tests. These are scenario-specific results and should not be taken as a general performance uplift for all Btrfs setups.
Memory management also benefits.
MGLRU (Multi-Gen LRU), Linux’s mechanism for deciding which pages to keep or reclaim when RAM is low, receives several updates.
One improves handling of dirty pages waiting to be written. Previously, the process responsible for writing these pages could react later than with traditional LRU. Linux 7.2 shifts part of this management into the memory recovery cycle, enabling earlier reactions during high write activity. Developers note this change especially benefits workloads with intensive writeback.
On a typical PC, this doesn’t immediately mean more RAM. The main advantage appears when the system is under memory pressure, constantly deciding what to keep, write, or free.
HDMI 2.1 FRL begins to make Radeon support complete
For AMD GPU users, the most visible innovation is HDMI 2.1 FRL.
FRL, Fixed Rate Link, replaces the traditional TMDS protocol used in HDMI when higher bandwidth is required. It’s essential for leveraging modern HDMI 2.1 features in resolutions and refresh rates beyond what TMDS can handle.
AMD has been working to bring this support into their open-source graphics driver, and Linux 7.2 finally includes much of this infrastructure.
Included are definitions for HDMI FRL, modifications in the Display Mode Library (DML), and baseline support for FRL in DML 2.0.
There’s also work on Display Stream Compression (DSC) over FRL, enabling visually lossless compression to achieve high-bandwidth modes on compatible displays.
This evolution is significant for Radeon users connecting to gaming TVs, making HDMI 2.1 features more accessible than ever. For years, HDMI 2.1 has been a sore point, with full support not fully available in Linux — now, progress is evident, although not all features are complete.
AMD continues to develop features like Variable Refresh Rate (VRR), FreeSync, and Auto Low Latency Mode (ALLM) over FRL. These patches are progressing after Linux 7.2’s release, so it’s more accurate to describe this as a major step toward full HDMI 2.1 support rather than complete implementation.
Linux 7.2 packs more than just a desktop update
The release also includes notable improvements that most home users may not notice directly.
Enhancements for NFS, SMB, networking, and KVM add new functions and fixes. Virtualization gains features related to AMD and Intel processors and continues extending support for VM isolation technologies.
Another small but revealing change is Rust support on the s390 architecture, the designation used by Linux for IBM Z mainframes.
Linux 7.2 was nearly to adopt a new GPU scheduler via DRM, switching to the fair policy as default. However, recent regressions prompted maintainers to revert and mark that change as experimental, restoring FIFO as the default behavior.
This exemplifies Linux kernel development: a feature can be considered complete and still be rolled back if real-world testing uncovers issues.
The final phase of the release also fixed issues with AMDGPU, Intel Xe, Wi-Fi, Ceph, network drivers, and more. Additionally, a change to the I2C subsystem was reverted after it caused some ThinkPads’ touchpads to stop working.
Linux 7.2 is not about a single game-changing feature but about accumulating improvements in core components constantly influencing the system’s operation.
The scheduler now better understands cache topology. Btrfs handles memory and I/O more efficiently. MGLRU refines its management under memory pressure. And AMD paves the way for practical HDMI 2.1 FRL support.
These changes are deeply integrated into the software stack and, because of that, have the potential to impact everything built upon them.
Frequently Asked Questions
Does Linux 7.2 improve performance on any PC?
Not necessarily. Improvements depend on hardware, storage, GPU, and workload type. For example, Cache Aware Scheduling is tailored for certain multi-threaded processes and may not apply or be beneficial in other scenarios.
Does Btrfs already support 2 MiB pages?
Linux 7.2 adds support for huge pages up to 2 MiB and enables large pages by default. However, support for even larger sizes remains experimental and should be used with caution.
Does Linux 7.2 fully enable HDMI 2.1 on Radeon?
Not yet. It provides essential parts of HDMI 2.1 FRL and DSC support, but features like VRR and FreeSync over FRL are still evolving.
Is manual installation of Linux 7.2 necessary?
Not for most users. Distributions will integrate the kernel over time, each following its own schedule for adoption.
