I wish there was a third class of concurrent thread, where N threads compete for a pool of M LWPs, and the thread limit could be rather limited by virtual memory only. Of course, there might need to be a smart dispatcher or dispatcher support, like a special yield where the thread could say it found nothing to do, so if all threads are idle, the dispatcher could poll(0,0,1) and release the lwp for the moment. Far more LWPs would be another way to do this (512 is nice but 65536 would be a lot better), but of course this passes the dispatching puzzle to the kernel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It may be obsolete/orphaned/whatever or not, but
I don't know what made me assume in my previous
message, that it would be related to tcl in any
way... (actually, I don't know if it is or not)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I wish there was a third class of concurrent thread, where N threads compete for a pool of M LWPs, and the thread limit could be rather limited by virtual memory only. Of course, there might need to be a smart dispatcher or dispatcher support, like a special yield where the thread could say it found nothing to do, so if all threads are idle, the dispatcher could poll(0,0,1) and release the lwp for the moment. Far more LWPs would be another way to do this (512 is nice but 65536 would be a lot better), but of course this passes the dispatching puzzle to the kernel.
I think this project is obsolete.
Maybe you get more answers for the
"thread" module of "tcl" project.
(This is not an official statement)
It may be obsolete/orphaned/whatever or not, but
I don't know what made me assume in my previous
message, that it would be related to tcl in any
way... (actually, I don't know if it is or not)