> 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.
There are plenty of cases Linux is most definitely not helping the situation
notably asynchronous block I/O.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:27 EST