>fire pajeets >hire competent engineers >re-write modern software to be fast/efficient >cache is no longer cache, it's literally main memory >DRAM still off to the side for shit like video data >OS+apps all in what we today call L3 >computers run faster than ever and secure
Why can't we have this?
this
jeets love the endless drivvle that is modern boiler plate code because it's meant to be as extensible as possible and ends up being huge.
devshitters will b***h and complain about not wanting to reinvent the wheel but then use a 14 step 3 sizes too large will downsize dynamically during the ride wheel from jeethub and call it a day.
oh nvm I misread your post, you want everything to be in L3 cache and RAM to be like a slow cache instead. We can't have that because everything is pajeet ware these days
is no longer cache, it's literally main memory >>DRAM still off to the side for shit like video data >>OS+apps all in what we today call L3
That's what the future of CPU cache will be if israelites and jeets get their act together maybe we'll see it in a decade if we're lucky
They should have an simple, in-order CPU with a flat 64 MB SRAM and use that for operations that require security. I don't know how it'd work but of course it would work I wouldn't propose it otherwise.
This would be a bigger performance hit than killing speculative execution which was the actual problem. The other solution that I assume wouldn't work otherwise Intel would have done it is to have some way for the CPU to know when pages belong to different processes.
The cash isnt the problem. It's halfbaked (or intentional backdoored) performance boost tricks. If you had no cache the same type of exploits would still exits
>muh security
Just kill all Black folk, pajeets, chinks and slavoids so we can enjoy a world without password thieves. You're just getting around the problem.
No.
ya lets destroy computer performance
>fire pajeets
>hire competent engineers
>re-write modern software to be fast/efficient
>cache is no longer cache, it's literally main memory
>DRAM still off to the side for shit like video data
>OS+apps all in what we today call L3
>computers run faster than ever and secure
Why can't we have this?
>fire jeets
>Why can't we have this?
Pick one
Jeets are the reason for GB sized software.
this
jeets love the endless drivvle that is modern boiler plate code because it's meant to be as extensible as possible and ends up being huge.
devshitters will b***h and complain about not wanting to reinvent the wheel but then use a 14 step 3 sizes too large will downsize dynamically during the ride wheel from jeethub and call it a day.
>Why can't we have this?
the laws of physics, specifically the speed of electrons
oh nvm I misread your post, you want everything to be in L3 cache and RAM to be like a slow cache instead. We can't have that because everything is pajeet ware these days
Nu-/g/, everybody.
is no longer cache, it's literally main memory
>>DRAM still off to the side for shit like video data
>>OS+apps all in what we today call L3
That's what the future of CPU cache will be if israelites and jeets get their act together maybe we'll see it in a decade if we're lucky
>hire competent engineers
Cache was invented by competent engineers.
the aerospace sector disables the cache entirely to get consistent performance and their real time mission critical software is fast enough without it
safety > performance
They should have an simple, in-order CPU with a flat 64 MB SRAM and use that for operations that require security. I don't know how it'd work but of course it would work I wouldn't propose it otherwise.
what if CPUs had a flag to enable/disable constant time execution for developers of security software?
I think only IBM mainframe cpus (S390) and the old Itanium had options for deterministic code execution.
>in-order CPU
From 14700K to P4 in one easy lesson.
It would be an additional core type. P cores, cuck cores and safe cores.
I saw this exact comment on the reg earlier. I see you fricker
This would be a bigger performance hit than killing speculative execution which was the actual problem. The other solution that I assume wouldn't work otherwise Intel would have done it is to have some way for the CPU to know when pages belong to different processes.
>speculative execution
If we got rid of Ram and use 100% cache (32gb cache lol), speculative execution would not be necessary
Enjoy your $50,000 processor.
Imagine dreaming about fantasy CPU archs because you suck at writing cache-friendly code.
>hardware cache exploits
>"just write cache friendly code dude"
>coomputers should be slow because MUH SHITCURITY
What a circus
>some way for the CPU to know when pages belong to different processes
ASID?
no
>posted from my CONFIG_SPECULATION_MITIGATIONS=n machine
The cash isnt the problem. It's halfbaked (or intentional backdoored) performance boost tricks. If you had no cache the same type of exploits would still exits
Most CVEs are RAM related so if we got rid of RAM that should really improve things too.
>use a slower computer to own the glow Black folk
theyll just use another vector
Instead of making it transparent make it actually interfaceable like regular ram, and add flags to the cpu to enable/disable speculative exec
speculative execution isn't the only side-channel attack
>muh security
Just kill all Black folk, pajeets, chinks and slavoids so we can enjoy a world without password thieves. You're just getting around the problem.
>WHAT IS FREE() SOMEONE PLEASE TELL ME i DONT KNOW WHAT FREE IS SAAARRR
Just pop out your COASt module.