News for hackers. Stuff that matters.
Re:SIMD Everywhere: 0.5.0 by NullPrefix on Tuesday August 04, 2020 @08:18AM (#24049180)
How do cloud vendors handle this on shared machines? Disable AVX?
Re:SIMD Everywhere: 0.5.0 by w0utert on Tuesday August 04, 2020 @09:07AM (#24049548)
Not sure how many cloud vendors are running CPU's with AVX-512 support, but I imagine that if they do you either have to pay for exclusive use of a single CPU (all cores), or thath they indeed disable AVX-512 instructions by patching the cpuid flags?

Note that the downclocking is only really a problem with AVX-512 and much less so with AVX2 and (AFAIK) not at all with AVX.

Re:SIMD Everywhere: 0.5.0 by BeeOnRope on Tuesday August 04, 2020 @01:21PM (#24052242)
The cloud vendors (at least the ones I checked) have SKUs with fairly limited downclocking, but more importantly the license based downclocking is per-core. So as long as you get at least a core to yourself, the noisy neighbor problem is reduced in that you affect your own CPU speed only.

For more fine-grained sharing, sure, if the key before you was running AVX-512 you'll get a lower frequency for the initial part of your timeslice, but it should pop back to full speed in under 1 ms.

Re:SIMD Everywhere: 0.5.0 by kristianp on Tuesday August 04, 2020 @05:36PM (#24054750)
Do the cloud vendors pin their VMs to a core to achieve this?
Re:SIMD Everywhere: 0.5.0 by BeeOnRope on Wednesday August 05, 2020 @11:34AM (#24061960)
Something like that, for the ones that dedicate at least a core per tenant. This also reduces the chance of cross-tenant information leakage.

Of course there are lots of scenarios where this isn't the case.

Re:SIMD Everywhere: 0.5.0 by wtallis on Tuesday August 04, 2020 @09:30AM (#24049730)
The big cloud guys get custom parts with non-standard clock speeds, which may include changes to how AVX512 clocking is handled.