AMD P-State Preferred Core handling for modern Ryzen systems. This is for leveraging ACPI CPPC data between CPU cores for improving task placement on AMD Ryzen systems for cores that can achieve higher frequencies and also helping in hybrid selection between say Zen 4 and Zen 4C cores. This AMD Preferred Core support has been in development since last year.
Performance gains on AMD 4th Gen EPYC
AMD FRU Memory Poison Manager merged along with other work as part of better supporting the AMD MI300 series.
AMD has continued upstreaming more RDNA3+ refresh and RDNA4 graphics hardware support into the AMDGPU driver.
#Intel
Intel Xeon Max gains in some AI workloads
Intel FRED was merged for Flexible Return and Event Delivery with future Intel CPUs to overhaul CPU ring transitions.
Reworked x86 topology code for better handling Intel Core hybrid CPUs.
Intel Fastboot support is now enabled across all supported graphics generations.
Intel Core Ultra "Meteor Lake" tuning that can yield nice performance improvements for those using new Intel laptops.
Continued work on the experimental Intel Xe DRM kernel graphics driver that Intel is aiming to get ready in time for Xe2 / Lunar Lake.
Video, Filesystem & Network
Support for larger frame-buffer console fonts with modern 4K+ displays.
Dropping the old NTFS driver.
Improved case-insensitive file/folder handling.
Performance optimizations for Btrfs.
More efficient discard and improved journal pipelining for Bcachefs.
FUSE passthrough mode finally made it to the mainline kernel.
More online repair improvements for XFS.
Much faster exFAT performance when engaging the "dirsync" mount option.
It refers to modern Intel CPUs where there are two types of cores - performance cores (P-cores) and efficient cores (E-cores). This is similar to ARM's big.LITTLE architecture which we've seen in smartphones for many years already.
Indeed. But I think some confusion will still remain as long as the ntfs-3g FUSE driver is still included by distros. Because right now, you have to explicitly specify the filesystem type as ntfs3 if you want to use the new in-kernel driver, otherwise it would use ntfs-3g. And most guides on the web still haven't been updated to use ntfs3 in the fstab, so I'm afraid this confusion will continue to persist for some time.
I've had bad experiences with ntfs3 anyway, so it's probably for the best that ntfs-3g is the default. Also last I checked ntfs3 had effectively been orphaned by paragon (the developers), is that still the case?
You know I didn't realize until now there was actually "confusion". I just thought I was a dolt for forgetting the package name or confusing the command name. Heh!