Meltdown and Spectre Patches with BIG Performance LOSS - Chris Titus Tech
video description
Date: 2022-03-20
Related videos
Comments and reviews: 9
gilkesisking
I remember the flapping hysteria that hit the Linux community when this vulnerability was first made public and the -debate/anger- over the cpu hits that eventually amounted to nothing on the first round of patches. Can't comment on V2 and correct me if I'm wrong ( its been awhile since I looked into this ). This vulnerability has something to do with intel cpu's -predicatively- loading code based on whats its doing at the time to speed up operations ( a method used for decades ) the issue is it was loading the predictive code without checks.. someone else described it like this... A person lands at an airport and walks straight though customs without showing a passport. Passport control says that's ok but can you please come back in two days and we'll check your passport then. They then have two days to run amok and can't be trusted to come back for checks. Apparently intel have known this for a long time and have kept using this predictive method to maintain the edge over AMD cpu speeds.
Its, again apparently, a really difficult exploit to take advantage of, if I remember correctly, so its a good decision on Linus's part and something desktop users shouldn't really be concerned about regardless of the OS.... its also the reason I've been holding off buying new cpu's for my own rigs and won't until it's mitigated in the architecture, as others have said.
reply
I remember the flapping hysteria that hit the Linux community when this vulnerability was first made public and the -debate/anger- over the cpu hits that eventually amounted to nothing on the first round of patches. Can't comment on V2 and correct me if I'm wrong ( its been awhile since I looked into this ). This vulnerability has something to do with intel cpu's -predicatively- loading code based on whats its doing at the time to speed up operations ( a method used for decades ) the issue is it was loading the predictive code without checks.. someone else described it like this... A person lands at an airport and walks straight though customs without showing a passport. Passport control says that's ok but can you please come back in two days and we'll check your passport then. They then have two days to run amok and can't be trusted to come back for checks. Apparently intel have known this for a long time and have kept using this predictive method to maintain the edge over AMD cpu speeds.
Its, again apparently, a really difficult exploit to take advantage of, if I remember correctly, so its a good decision on Linus's part and something desktop users shouldn't really be concerned about regardless of the OS.... its also the reason I've been holding off buying new cpu's for my own rigs and won't until it's mitigated in the architecture, as others have said.
reply
Houyhnhnm
This was 2018, it's a lot worse now. There are new patches for new exploits and the 9900k performs no different from the i7 920 now. Looking pretty grim for Intel. RPCS3 used to run Red Dead Redemption at 4k 45fps, now it's at 8fps after the patching. Ryzen 3000 will run RDR 4k -60fps. Ryzen 3k will cost less than the 8700k, no brainer. Sell your intel chips and prepare to buy Ryzen 3000 chips.
reply
This was 2018, it's a lot worse now. There are new patches for new exploits and the 9900k performs no different from the i7 920 now. Looking pretty grim for Intel. RPCS3 used to run Red Dead Redemption at 4k 45fps, now it's at 8fps after the patching. Ryzen 3000 will run RDR 4k -60fps. Ryzen 3k will cost less than the 8700k, no brainer. Sell your intel chips and prepare to buy Ryzen 3000 chips.
reply
Jeff
Hmm, not sure how I feel about leaving linux as the only os open to this vulnerability. Doesn't that make it the low hanging fruit of operating systems then, focusing the attention of those who would seek to exploit this vulnerability 100% on Linux? I agree with Linus though as the 50% hit in performance is a killer.
reply
Hmm, not sure how I feel about leaving linux as the only os open to this vulnerability. Doesn't that make it the low hanging fruit of operating systems then, focusing the attention of those who would seek to exploit this vulnerability 100% on Linux? I agree with Linus though as the 50% hit in performance is a killer.
reply
Omega
So about your comment about forcing your work place to use two factor. Two step verification doesn't increase security if you you SMS as that can be bypassed by social engineering, you need to use a authenticator that only you have access to.
reply
So about your comment about forcing your work place to use two factor. Two step verification doesn't increase security if you you SMS as that can be bypassed by social engineering, you need to use a authenticator that only you have access to.
reply
phr
The ultimate in security is having no users, no access and completely static data. Meltdown is a vulnerability that would never be applied maliciously since there are other simpler ways to achieve the same goals in every system out there.
reply
The ultimate in security is having no users, no access and completely static data. Meltdown is a vulnerability that would never be applied maliciously since there are other simpler ways to achieve the same goals in every system out there.
reply
Daniel
I am really looking forward to when Spectre and Meltdown are mitigated by the CPU architecture itself; I really don't want to buy a new PC until Intel and AMD take care of this themselves.
reply
I am really looking forward to when Spectre and Meltdown are mitigated by the CPU architecture itself; I really don't want to buy a new PC until Intel and AMD take care of this themselves.
reply
ritual301
Appreciate the heads up. I've got confidence the kernel devs will iron out some of those wrinkles by the time kernel 5/4.20 goes stable. Thanks for vid;)
reply
Appreciate the heads up. I've got confidence the kernel devs will iron out some of those wrinkles by the time kernel 5/4.20 goes stable. Thanks for vid;)
reply
Dennis
bugs : cpu_meltdown spectre_v1 spectre_v2 just found it on Linux Mint 19.1 Cinnamon went looking because linux slowed way way down.
reply
bugs : cpu_meltdown spectre_v1 spectre_v2 just found it on Linux Mint 19.1 Cinnamon went looking because linux slowed way way down.
reply
Red
-1:07 I am happy that I am using the 4.15 LTS now. It appears to be that old Haswell-E E3 Xeons with hyperthreading are effected. :)
reply
-1:07 I am happy that I am using the 4.15 LTS now. It appears to be that old Haswell-E E3 Xeons with hyperthreading are effected. :)
reply
Add a review, comment
Other channel videos
