> the IBM paper), that if your application depends on huge numbers of 
> threads, you're always going to keep bumping up against the scheduler? 
> a lot of people throw lots of threads at a problem and it can really 
> be bad design. 


That is the least of your worry. 1000 threads is 8Mb of kernel stacks, and 
enough switching of tasks to be sure you might as well turn most of your 
cache off. A computer is a state machine. Threads are for people who cant 
program state machines.

##</code><code>##

...
{ lock $variable; $x = something }
...