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.
Many networking improvements.

Full summary here: https://www.phoronix.com/review/linux-69-features/

save

path: 0 10017004, hotness: undefined, score: 103, children: 12

boredsquirrel 16 points 2 years ago

I wonder what an Intel Core hybrid CPU is

save

path: 0 10017004 10018206, hotness: undefined, score: 16, children: 11

d3Xt3r 37 points 2 years ago

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.

See: https://www.intel.com/...

save

path: 0 10017004 10018206 10018349, hotness: undefined, score: 37, children: 0

fuckwit_mcbumcrumble 18 points 2 years ago

12th gen and up intel CPUs. All but a few have P and E cores.

Also like one weird i5 from about 10th gen.

save

path: 0 10017004 10018206 10019235, hotness: undefined, score: 18, children: 9

boredsquirrel 2 points 2 years ago

I have a mobile 11th i7 one, sounds like no benefits 😞

save

path: 0 10017004 10018206 10019235 10026503, hotness: undefined, score: 2, children: 8

fuckwit_mcbumcrumble 2 points 2 years ago

Same boat. Good news is 11th gen generally gets better battery life than 12th+ because all those extra cores still eat power.

Bad news is I already get as bad as 30 minutes of battery life so IDK how 12th gen can be even worse.

save

path: 0 10017004 10018206 10019235 10026503 10030173, hotness: undefined, score: 2, children: 7

simple 45 points 2 years ago

Dropping the old NTFS driver.

Good stuff. Hasn't there always been confusion on mounting your NTFS drive using the old driver vs the new?

save

path: 0 10017283, hotness: undefined, score: 45, children: 9

d3Xt3r 46 points 2 years ago

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.

save

path: 0 10017283 10017493, hotness: undefined, score: 46, children: 8

SteveTech 6 points 2 years ago

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?

save

path: 0 10017283 10017493 10018583, hotness: undefined, score: 6, children: 6

d3Xt3r 15 points 2 years ago

ntfs3 has had several improvements in 6.2 and 6.8, and it's been pretty stable for me of late. I use it to share/backup my Steam game library mainly + for my portable drives for general data storage/local backups, and haven't had any issues.

It's not orphaned. There was a bit of lull after it was introduced in kernel 5.15, and yes it was a bit unstable in the 5.x series, but it's been pretty good since 6.2 where they finally introduced the nocase and windows_names mount options. The performance improvements are worth it if you use NTFS heavily, so I would personally recommend switching.

save

path: 0 10017283 10017493 10018583 10018977, hotness: undefined, score: 15, children: 5

SteveTech 1 point 2 years ago

Ahh thanks! That's good to know!

save

path: 0 10017283 10017493 10018583 10018977 10022213, hotness: undefined, score: 1, children: 0

taaz 1 point 2 years ago

For me, Steam (on Linux) has been periodically corrupting the ntfs disk, I do use it on windows too and not even win hybrid/fastboot/hibernation disabled helps.

May I see what mount options you use for the ntfs3 driver in fstab? I do not currently have the nocase and windows_names ...

save

path: 0 10017283 10017493 10018583 10018977 10027710, hotness: undefined, score: 1, children: 1

lemmyvore 1 point 2 years ago

Is this for read-only use? Or is it usable also for modifying files?

save

path: 0 10017283 10017493 10018583 10018977 10027459, hotness: undefined, score: 1, children: 1

glouriousgouda 4 points 2 years ago

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!

save

path: 0 10017283 10017493 10033864, hotness: undefined, score: 4, children: 0

PiratePanPan 44 points 2 years ago