3 ms·
I don't see your point. "Linux thread context switch time" is a meaningless metric, since Linux will switch thread context regardless of what you choose to run
by otabdeveloper4 6y ago
I don't see your point.
"Linux thread context switch time" is a meaningless metric, since Linux will switch thread context regardless of what you choose to run on your computer.
Any "async" switches are additional overhead; you don't get to not have kernel preemption just because your Rust thread is now switching contexts "asyncly".
There are benefits to having an additional user-mode scheduling mechanism inside your kernel thread, but saving CPU cycles isn't one of them.
- ithkuil 6y ago> switches thread contexts regardless of what you're running my point was that thread context switches caused by preemption happen at an entirely different time scale than the rate of context switches caused by syscalls (if the system is doing any meaningful level of IO)