3 ms·
>> It in fact would be perfectly valid and good to implement AVX-512 with a 256-bit unit that takes twice as long to run 512-bit width instructions. This compl
by phkahler 6y ago
>> It in fact would be perfectly valid and good to implement AVX-512 with a 256-bit unit that takes twice as long to run 512-bit width instructions. This completely negates all his points about die space utilization right from the start - AVX-512 support does not imply a significantly larger use of space than previous AVX instructions.
The extra registers have to be there even if the execution unit is half size. The context switching overhead grows, which is something kernel developers care about. And then with all these variants there's a push to have a single binary support them all which complicates the code too. Meanwhile the world is moving toward parallelism which is going to mean more thread creation and context switching.
Linus does have valid concerns here.
- MrBuddyCasino 6y agoAre those AVX-512 registers saved on context switches? At least on syscalls, the kernel could just have a policy of not using those registers? I'm not exactly sure how that works, this is part of the ABI right?