5 ms·
Great then all processes will be running on the P-cores only, with the E-cores idling all day. Note that even simple things like memcpy, which every single pro
by nolist_policy 3y ago
Great then all processes will be running on the P-cores only, with the E-cores idling all day.
Note that even simple things like memcpy, which every single program out there will use, will use AVX512!
- kimixa 3y agoGenerally it seems things that benefit from super wide simd also benefit from threading. If productivity apps want to leave performance on the table, so be it. But really I think the entire ecore/pcore split for avx512 is academic, as I'm not sure tying features and flexibility to wider registers makes sense even on pcores, as I'm not sure the hardware area cost is worth the benefit. I honestly wouldn't be surprised if newer architectures don't have the wider registers options on even their larger cores. You're chasing a pretty small market IMHO of people who have datasets large enough to benefit from large registers and wider alus, but not so large it's worth it to pass it over to an even more specialized accelerator. The benchmarks that tend to show 512-wide simd benefits may get even bigger benefits from running on a GPU.
- sylware 3y agoActually not, on "recent"/"not too old" x86_64 architecture, "rep movsX" instructions are now hardware accelerated for short and big memory blocks. Memcpy and other basic memory operations are getting their code generated directly by the compiler which shortcuts the OS runtime.