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.
fuckwit_mcbumcrumble@lemmy.dbzer0.com
on 13 May 2024 00:37
collapse
12th gen and up intel CPUs. All but a few have P and E cores.
Also like one weird i5 from about 10th gen.
boredsquirrel@slrpnk.net
on 13 May 2024 10:49
collapse
I have a mobile 11th i7 one, sounds like no benefits 😞
fuckwit_mcbumcrumble@lemmy.dbzer0.com
on 13 May 2024 15:02
collapse
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.
boredsquirrel@slrpnk.net
on 13 May 2024 15:34
nextcollapse
My battery life is pretty good, the power profiles daemon is actually working very well.
redditReallySucks@lemmy.dbzer0.com
on 13 May 2024 16:45
collapse
I thought you saved power because the e-cores are more efficient for the same workload?
fuckwit_mcbumcrumble@lemmy.dbzer0.com
on 13 May 2024 18:46
nextcollapse
Yeah but this is Intel, they’re not capable of doing something the most efficient way possible. E cores use less power than P cores, but that doesn’t mean they’re very good at getting the job done using the least amount of power. Currently (using Intel’s management) 12th and 13th gen start a task on the P cores, and if it runs for longer than X time it gets shifted over to the E cores where it can churn away. Meteor lake has 3 stages of things since there’s P cores, E cores, and LP E cores. If I remember right Meteor lake starts a task on the LP E cores, then shifts it to P cores, then shifts it to the E cores if it’s taking too long. But Intel likes to blast the power away with turbo boost and runs the E cores way past their actual efficient zone unless you wrangle them back down. Sometimes it’s faster to blast the task away on the P cores then return to idle, other times letting it churn away on the E cores forever is the best way.
Also all those extra cores being active still uses power. So if you went from a 4 core CPU to a 4 + 4 cpu now you have all the same power draw as the old one, plus the extra 4 efficient cores sipping at even more power. I think that’s where 12th gen really suffers the most.
iopq@lemmy.world
on 14 May 2024 04:18
nextcollapse
Spoilers: they are efficient in space, not really power
So for multicore workloads they are actually power efficient because you get more throughput (more performance iso power)
But for idle that has no benefit
TheGrandNagus@lemmy.world
on 14 May 2024 14:30
collapse
They’re not really made for power efficiency, but rather space efficiency. ~4 E-cores fit into the size of a P-core.
They’re there to boost multi-core performance without having a huge die-size or increasing latency in the P-cores when doing lightly threaded tasks, essentially.
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.
SteveTech@programming.dev
on 12 May 2024 23:44
nextcollapse
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?
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.
It’s r/w, if you specify the filesystem type as ntfs3. I believe if you use just ntfs it’ll be read-only, to mimic the behaviour of the old driver, for compatibility reasons.
taaz@biglemmowski.win
on 13 May 2024 12:15
collapse
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 …
If you’re copy-pasting this, make sure your uid and gid matches of course.
But the key thing for Steam is you need to have your compatdata folder on a Linux partition, because Proton creates folders with invalid characters (like :). windows_names would prevent that of course, and thus prevents corruption, but it would cause Proton to fail since if can’t create those folders/files. So you’ll need to symlink that folder on your NTFS disk to point to a folder on a Linux partition.
Of course, before you run the above, you’ll need to delete the existing compatdata folder from the NTFS disk.
glouriousgouda@lemmy.myserv.one
on 13 May 2024 19:01
collapse
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!
FaizalR@kbin.social
on 13 May 2024 00:44
nextcollapse
I am hoping for a smooth sailing of the new kernel.
TheGrandNagus@lemmy.world
on 13 May 2024 07:58
nextcollapse
69, interrupted with a period? Not nice
BitingChaos@lemmy.world
on 13 May 2024 16:11
collapse
Ni.ce
drwho@beehaw.org
on 13 May 2024 15:59
nextcollapse
“nice” * 0.1
mindbleach@sh.itjust.works
on 13 May 2024 16:50
nextcollapse
GNU/Nice.
KarnaSubarna@lemmy.ml
on 13 May 2024 17:48
nextcollapse
Used Mainline to install it on Ubuntu 23.10. Together with Nvidia driver v550, it is working without an issue for me.
PiratePanPan@lemmy.dbzer0.com
on 13 May 2024 18:05
nextcollapse
INTERNET FUNNY NUMBER LET’S FUCKING GOOOOOOOOOOOOO
tkk13909@sopuli.xyz
on 14 May 2024 01:22
nextcollapse
threaded - newest
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Noice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice
Nice, France
Nice, what?
Nice.
Nice
Nice
Nice
.
lmao at the guy downvoting all the Nice
Presumably, his vote is public ?
You wait your turn, u/9point6.
The nice chain shows how nice Lemmy is because the 4th one didn’t get downvoted to oblivion
Here’s the TL;DR from Phoronix:
#AMD
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: www.phoronix.com/review/linux-69-features/
I wonder what an Intel Core hybrid CPU is
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: www.intel.com/…/how-hybrid-design-works.html
12th gen and up intel CPUs. All but a few have P and E cores.
Also like one weird i5 from about 10th gen.
I have a mobile 11th i7 one, sounds like no benefits 😞
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.
My battery life is pretty good, the power profiles daemon is actually working very well.
I thought you saved power because the e-cores are more efficient for the same workload?
Yeah but this is Intel, they’re not capable of doing something the most efficient way possible. E cores use less power than P cores, but that doesn’t mean they’re very good at getting the job done using the least amount of power. Currently (using Intel’s management) 12th and 13th gen start a task on the P cores, and if it runs for longer than X time it gets shifted over to the E cores where it can churn away. Meteor lake has 3 stages of things since there’s P cores, E cores, and LP E cores. If I remember right Meteor lake starts a task on the LP E cores, then shifts it to P cores, then shifts it to the E cores if it’s taking too long. But Intel likes to blast the power away with turbo boost and runs the E cores way past their actual efficient zone unless you wrangle them back down. Sometimes it’s faster to blast the task away on the P cores then return to idle, other times letting it churn away on the E cores forever is the best way.
Also all those extra cores being active still uses power. So if you went from a 4 core CPU to a 4 + 4 cpu now you have all the same power draw as the old one, plus the extra 4 efficient cores sipping at even more power. I think that’s where 12th gen really suffers the most.
Spoilers: they are efficient in space, not really power
So for multicore workloads they are actually power efficient because you get more throughput (more performance iso power)
But for idle that has no benefit
They’re not really made for power efficiency, but rather space efficiency. ~4 E-cores fit into the size of a P-core.
They’re there to boost multi-core performance without having a huge die-size or increasing latency in the P-cores when doing lightly threaded tasks, essentially.
Good stuff. Hasn’t there always been confusion on mounting your NTFS drive using the old driver vs the new?
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
ntfs3if you want to use the new in-kernel driver, otherwise it would usentfs-3g. And most guides on the web still haven’t been updated to usentfs3in the fstab, so I’m afraid this confusion will continue to persist for some time.I’ve had bad experiences with
ntfs3anyway, so it’s probably for the best thatntfs-3gis the default. Also last I checkedntfs3had effectively been orphaned by paragon (the developers), is that still the case?ntfs3has 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
nocaseandwindows_namesmount options. The performance improvements are worth it if you use NTFS heavily, so I would personally recommend switching.I would have loved to take that performance before I converted my data drives to ext4, however it’s just inherently not stable.
Sometimes If you have a power loss you have to run chkdsk on Windows to get out of ro mode, no?
There’s no need to run
chkdskfrom Windows, you can runntfsfixdirectly from Linux:Ahh thanks! That’s good to know!
Is this for read-only use? Or is it usable also for modifying files?
It’s r/w, if you specify the filesystem type as
ntfs3. I believe if you use justntfsit’ll be read-only, to mimic the behaviour of the old driver, for compatibility reasons.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
ntfs3driver in fstab? I do not currently have the nocase and windows_names …Mine looks like this:
UUID=blah /media/games ntfs3 uid=1000,gid=1000,umask=000,rw,user,exec,nofail,nocase,windows_names 0 0If you’re copy-pasting this, make sure your uid and gid matches of course.
But the key thing for Steam is you need to have your
compatdatafolder on a Linux partition, because Proton creates folders with invalid characters (like:).windows_nameswould prevent that of course, and thus prevents corruption, but it would cause Proton to fail since if can’t create those folders/files. So you’ll need to symlink that folder on your NTFS disk to point to a folder on a Linux partition.Eg:
Of course, before you run the above, you’ll need to delete the existing
compatdatafolder from the NTFS disk.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!
I am hoping for a smooth sailing of the new kernel.
69, interrupted with a period? Not nice
Ni.ce
“nice” * 0.1GNU/Nice.
Used Mainline to install it on Ubuntu 23.10. Together with Nvidia driver v550, it is working without an issue for me.
INTERNET FUNNY NUMBER LET’S FUCKING GOOOOOOOOOOOOO
NICE
Nice