
Linux 7.3:The biggest kernel ever delivers faster storage and smarter scheduling
Wow. That's one big Linux kernel release! Released on October 18, the 7.3 kernel set development records with 18,765 non-merge commits from 3,021 developers, including 807 first-time contributors.
以下正文同步自 Hacker News 最新,版权归原站所有,已转换为易读排版。
Wow. That's one big Linux kernel release! Released on October 18, the 7.3 kernel set development records with 18,765 non-merge commits from 3,021 developers, including 807 first-time contributors.
Why was it so big? Well, it's not because it came with a horde of new features. No, two different forces drove its growth. First, there was an enormous number of AMD graphics hardware-definition headers. Then, and this shouldn't surprise anyone, it came filled with AI-related fixes and cleanup.
As for the first, Torvalds has explained earlier on the Linux Kernel Mailing List (LKML), "This is yet another one of those releases with a big AMD GPU register dump,” he wrote. “This time it’s the AMD DCN6 register headers. They’re huge. As usual.”
Part of the reason is that these headers encode hardware definitions as C preprocessor definitions. Combined with the accompanying code for the new graphics generation, they accounted for about one-third of the entire 7.3-rc1 patch—not one-third of the kernel itself.
Torvalds added: “But if you just mask out that big chunk, things look pretty normal, and this merge window didn’t feel that different from most of them despite being large."
As for the AI part, the networking subsystem alone, maintainer Jakub Kicinski reported, had merged 632 patches into the fixes stream and 648 into the next-release development stream. He estimated that one-third to one-half of the latter “seem like AI-driven low-priority fixes, cleanups and clarifications.”
“We are completely overwhelmed, of course,” Kicinski added. He said the maintainers were themselves using multiple frontier models to assist with patch review, while cautioning that “the LLMs can only do so much.”
Still, when all was said and done, 7.3 arrived on schedule. Linus Torvalds wrote, "It's Sunday afternoon, and this week I somehow kept my wits together long enough to keep track of the day of the week, so the release isn't randomly delayed. Will wonders never cease?" Given he'd just spent the week before at the Linux Plumbers Conference in Prague, color me impressed. I was there too, and I'm still not sure what day it is.
Beyond those headline numbers are improvements that matter to Linux desktops, storage servers, virtual-machine (VM) hosts, and container deployments.
Faster storage, with workload-specific gains
Some of Linux 7.3’s most immediately useful work is in its storage stack. Ext4, the most popular general-use file system, gains better parallel direct I/O writes and faster space allocation through fallocate(). The developers also fixed a buffered-write performance regression. A simplified path for small direct-I/O operations increased ext4 performance from 1.92 million to 2.19 million I/O operations per second in one reported sample workload. That is a specific benchmark result, not a promise that every ext4 installation will become proportionally faster. Still, that's a decent kick-in-the-pants for file reads and writes.
Btrfs also got some love with several improvements. For example, Btrfs has had r direct-I/O performance restored. Its developers also removed an unnecessary delay, improving latency and throughput for logging workloads on devices operating in non-SSD mode. Another optimization skips redundant hole detection during full fsync() operations for suitable files. Reported gains of roughly fivefold apply to those particular test cases, not Btrfs performance generally.
Filesystem in Userspace (FUSE) also saw performance improvements. Servers using io_uring can provide buffer pools, reducing memory requirements and giving the kernel more flexibility in assigning request buffers. A new zero-copy option lets a suitably privileged server access client pages or page-cache folios without an intermediate data copy.
For databases and other applications accessing raw block devices, Linux 7.3 extends RWF_DONTCACHE support to those devices. Applications can choose whether to retain data in the page cache per request, rather than treating direct I/O as an all-or-nothing policy.
正文由 探How 从来源站点 RSS 同步,内容未经改写;遇到排版缺失或需要图片、视频时请以原文为准。