3 ms·
A point often missed is that for green threads to work really well you have to pull most of what the operating system does into user space to eliminate blocking
by jandrewrogers 12y ago
A point often missed is that for green threads to work really well you have to pull most of what the operating system does into user space to eliminate blocking syscalls. That is a lot of work but if you do it competently it will greatly outperform (by integer factors) the same design going through the operating system. This is how high-performance database engines are designed.
As with all such low-level hackery you really need to understand what you are doing to get a good result, but if you do understand what you doing the results can be excellent.
- Rusky 12y agoThis is one of the reasons for MIT's exokernel design- most of what the operating system does gets pulled into userspace libraries by default, the same way it is with green threads, so you get the same kinds of benefits with file systems, networking, IPC, etc. I'm kind of disappointed most kernels that have added scheduler activations have dropped support because they didn't want to deal with both interfaces and weren't willing to drop the traditional one.