The choice of CPU naming was from my patches, so you could blame me for it. Really the mess is from Intel, of course. As has been pointed out, the "code names" are very commonly used, not just within Intel. They are also often used to group together different client and server processors that are architecturally very similar and can be expected to have the same cycles-per-byte performance. For example I did the "Ice Lake" benchmark on an Ice Lake server processor, which is also known as "3rd generation Xeon Scalable", but the result should also apply to Ice Lake client which is "10th generation Core".
Announcement
Collapse
No announcement yet.
Linux 6.10 Makes AES-XTS Disk/File Encryption Much Faster For Modern Intel/AMD CPUs
Collapse
X
-
Silly question, to take advantage of this (in addition to having a modern CPU), you'd need to compile the kernel with MARCH = native or x86-64-v4 right? So if you're just using the default kernel provided by a mainstream distro, you'd never see the benefits of this?
- Likes 1
Comment
-
-
Originally posted by [deXter] View PostSilly question, to take advantage of this (in addition to having a modern CPU), you'd need to compile the kernel with MARCH = native or x86-64-v4 right? So if you're just using the default kernel provided by a mainstream distro, you'd never see the benefits of this?
- Likes 2
Comment
Comment