Messages in this thread | | | From | (Larry McVoy) | Subject | Re: Thread implementations... | Date | Sat, 20 Jun 1998 12:51:43 -0700 |
| |
: Even with the debugging problems solved, linuxthreads are heavier : than solaris pthreads or NT fibers.
So how about quantifying that a bit and show us some numbers and how they affect things in real life?
: Unix multiplexing facilities -- select and poll -- are wake-all : primitives. When something happens, everything waiting is awakened : and immediately starts fighting for something to do. What a waste. : They make a lot of sense for processes though. On NT completion : ports provide wake-one semantics... which are perfect for threads. : : Yes, this does in fact suck. However, the path to go down is not to : expect the way select/poll work to change, rather look at other : existing facilities or invent new ones which solve this problem. : Too much user code exists which depends upon the wake-all semantics,
Hmm. SGI changed accept() from wakeup-all to wakeup-one with no problem.
I'd be interested in knowing which programs depend on the race.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |