3 ms·
When you get to kernel land it is "something async plus a wait"; there's no other way for it to be when the remote task is on a different core. But it's a spec
by astrange 5y ago
When you get to kernel land it is "something async plus a wait"; there's no other way for it to be when the remote task is on a different core.
But it's a special wait that the scheduler and other systems know how to benefit from using vouchers/turnstiles/etc. If you look at spindump output you should see it.