3 ms·
> Not all AVX instructions trigger a cooldown to build voltage Ok, but the AVX instructions that do trigger the cooldown may be the ones you wish to use, and t
by R0b0t1 6y ago
> Not all AVX instructions trigger a cooldown to build voltage
Ok, but the AVX instructions that do trigger the cooldown may be the ones you wish to use, and the statement is still valid. I never mentioned AMD.
> not "standalone units"
I didn't say they were standalone, in fact, the opposite. It just depends on what you want to call a boundary. The tighter integration is what is driving these special purpose units but up until now they've not affected package TDP so heavily.
- paulmd 6y ago> Ok, but the AVX instructions that do trigger the cooldown may be the ones you wish to use, and the statement is still valid. I never mentioned AMD. Again, it's not that AVX instructions inherently must be clocked down for. It is an implementation detail of Intel's processor. AMD already has different boost behavior for AVX2 and will probably have different boost behavior for AVX-512 when they implement that. > It just depends on what you want to call a boundary What you were saying is that they are units attached over some "fabric", which isn't the case. > The shared memory fabric allows fast offload the the extremely specialized processing units. They aren't "multiple processors that share memory", it is an execution unit within the Streaming Multiprocessor. It is no different from an AVX instruction, they are driven by registers, not by a fabric and not by memory. At risk of reigniting the old Bulldozer "what is a core really anyway", AVX and tensor cores don't really represent an independent core, they are an execution unit within a larger core. They can't operate independently without the other execution resources provided by the core.