thread pool

[ct]

Implement a thread pool where threads are readily available to pick up
work from the scheduler. Threads need to be created whenever requested
and it need to be watched that there are generally no more *running*
threads than some config setting (number of cores?). Since threads can
sleep there may be more threads. When the thread pool fills up it should
be generously garbage collected etc.

[ct]

A basic but functional threads implementation is already working.
No pooling so far and most features are ignored. There is a ongoing
discussion if we need a join() functionality, I can add that on demand.

There is no thread pooling yet, each thread_run() creates a new
thread. But pooling will be only a (huge) performance optimization.

[ichthyo]

reorganising core component tickets

[jyakovlev]

If nobody works on this ticket now, I wanna to take it. :)

[ct]

Replying to jyakovlev:

If nobody works on this ticket now, I wanna to take it. :)

This prolly needs some acknowledgement about the plans, but otherwise it would be fine when you work on it.

[plouj]

I'm assigning this to myself since jyakovlev has been idle and I've started work on it in my repo:  http://git.lumiera.org/gitweb?p=lumiera/plouj;a=summary

[ct]

thread pools are basically working, some things left to be done later. But for now i close this ticket. Better create single tickets for each additional thing to do.