Skip to content

Product1 publisher3 min readPublished

Linux 7.2 ships cache-aware scheduling, and Torvalds calls AI bug reports the new normal

The scheduler change is throughput you get for the cost of an upgrade. The more durable news is that late-cycle patch volume is now permanently larger, and the maintainer has stopped fighting it.

The Product Desk · Product desk

Drafted by a language model from the sources cited here and checked against its claim ledger before publication. How we use AISend a correction

Illustration accompanying Linux 7.2 ships cache-aware scheduling, and Torvalds calls AI bug reports the new normal
Generated illustration

What happened

  • Linus Torvalds announced the release of Linux kernel 7.2 over the weekend.
  • The marquee addition in Linux 7.2 is Cache Aware Scheduling, a scheduling change that has been in the works for several years.
  • In his note on Linux 7.2's seventh release candidate, Torvalds wrote: "I can't say that I'm exactly thrilled about the size of this all. But it is what it is: the new normal with a lot of fixes, many of them due to review by various AI tools."
  • Previously the scheduler balanced load across CPU cores without checking whether threads on separate cores shared memory, so threads on different cores would re-fetch the same data, causing cache bouncing in which the system wasted time and resources pulling and re-pulling the same data.
  • Torvalds on the patch series: "The goal of the patch series is to aggregate tasks sharing data to the same LLC cache domain, thereby reducing cache bouncing and cache misses, and improving data access efficiency."

Compiled by The Product DeskSomething wrong?How this is made

Why it matters

Linus Torvalds released Linux kernel 7.2 over the weekend, with Cache Aware Scheduling as the marquee addition [1][2]. For anyone packing many threads onto one socket, that is a throughput gain for the price of an upgrade; the more consequential line is elsewhere in his notes, where Torvalds describes AI-generated bug reports as a permanent condition of the release cycle rather than a spike [3].

The scheduler work is not new. The patch series has been in progress for several years [2]. Previously the load balancer spread threads across cores without checking whether threads on separate cores shared memory, so those cores re-fetched the same data and the system paid repeatedly for the same lines, a pattern known as cache bouncing [4]. Torvalds describes the goal as aggregating "tasks sharing data to the same LLC cache domain, thereby reducing cache bouncing and cache misses, and improving data access efficiency" [5]. The guardrails are what make this a multi-tenant feature rather than a benchmark result: the code avoids overloading a cache domain, and stops moving threads once a process consumes more than 25% of CPU time or more than one-third of a domain's load [6]. According to ZDNET, multithreaded servers, AI and ML compute jobs, and some games stand to benefit most [7].

The release note is blunter about process than about performance. Torvalds wrote that the last week of the release was "once again -- bigger than I would have wished for," adding that with "the whole 'new normal' thing," delaying releases for that reason would mean never releasing at all [8]. At release candidate seven he had already defined the term: "the new normal with a lot of fixes, many of them due to review by various AI tools" [3]. These are largely not features written by AI but patches for AI-discovered security vulnerabilities [9]. His objection is to how they are routed: "This is all entirely pointless churn, and we're making it clear that AI-detected bugs are pretty much by definition not secret, and treating them on some private list is a waste of time for everybody involved - and only makes that duplication worse because the reporters can't even see each other's reports" [10]. He is not banning the tools, telling contributors to "use them in a way that is productive and makes for a better experience" [11]. The operational reading is his own: the tail end of a cycle now routinely carries more fixes than the maintainer wants [8].

Elsewhere, exFAT moves to the kernel's iomap, which ZDNET reports improves read and write speed on SD cards and USB sticks by as much as 87% [12]. Experimental folios up to 2 MB arrive, and iomap conversion work continues for ext4 and XFS [13][14]. There is initial AMDGPU support for HDMI 2.1 Fixed Rate Link, enabling uncompressed 4K at 120Hz and 8K [15], Intel's USB4STREAM for raw host-to-host transfer over USB4 and Thunderbolt links that bypasses the networking stack [16], plus Wi-Fi Aware and early Wi-Fi 8 groundwork [17].

Two things to watch. Whether the security list handling for AI-detected bugs actually changes, since Torvalds has now said publicly that the private-list route makes duplication worse [10]. And whether the scheduler gain survives contact with real tenancy: most users will not see 7.2 until fall distributions such as Ubuntu 26.10, and the benefits are concentrated in machines with complex CPU-cache layouts and storage-heavy workloads [18][19].

Loading claim ledger
Loading source directory links
Loading share composer
Loading topic controls
Loading related stories