3 ms·
Presumably the AVX-512 code is something on your hot path, so I’m not sure waiting for a signal to reschedule the work is something you would want.
by saagarjha 5y ago
Presumably the AVX-512 code is something on your hot path, so I’m not sure waiting for a signal to reschedule the work is something you would want.
- heavenlyblue 5y agoYou reschedule it only once so it doesn’t matter
- saagarjha 5y agoI don’t see how? Once your quantum is up the thread gets put back into the scheduling pool and you have to do this all over again…
- boardwaalk 5y agoCouldn’t there be some flag on the thread that marks it as “P-core only”? Doesn’t seem hard. I don’t known Linux scheduler internals though.
- saagarjha 5y agoRight but then you’d just have all processes with that flag all the time.
- pantalaimon 5y agoOnly if glibc decides to use AVX512 for memset and such. I’m not sure if that makes sense to begin with, but it could also not do that if it detects a heterogeneous CPU.
- pantalaimon 5y agoThreads already have an affinity bit mask where you can select which cores they can be scheduled on. https://man7.org/linux/man-pages/man2/sched_setaffinity.2.html https://man7.org/linux/man-pages/man2/sched_setaffinity.2.ht...
- heavenlyblue 5y agoYou don’t have to schedule your thread on another core at all