Subj : Re: Futexes are wrong! (Are they?) To : comp.programming.threads From : David Schwartz Date : Tue Jun 07 2005 06:19 pm "Jomu" wrote in message news:1118182702.839068.297110@g44g2000cwa.googlegroups.com... > Why would this be more competition than N-clients-per-thread, except > in order of magnitude? The alternative is not N-clients-per-thread, but a pool of threads that handles all the clients. And the reason that's better is that you can do a little bit of work on several clients without a single context switch. > Won't we loose some of threads readability and > clarity when we multiplex clients in same code flow? Nope. Everybody things the way they're not used to doing things is harder or not as neat. > Isn't that > hybridization of threads with event driven programming? The point of threads is to keep multiple CPUs busy and to make blocking non-fatal to the process (so you don't have to write 100% of your code where any blocking is a total disaster). This gives you those important advantages. DS .