> On 17 Dec, Dan Kegel scribbled:
> -> re http://kernelnotes.org/lnxlists/linux-kernel/lk_9912_03/msg00480.html
> ->
> -> Rasterman is wrong in saying that all threads run on the same
>
> hmm - when did that change ? i thought that was the case and was baked
> up on hat asumtion by someone else a few weeks ago (primarily the
> reason being to make sure the threads share caches for speed reasons
> and to make sure cache concurrency issues are moe easiyl dealt with...
> well thats what i unerstood... i may be wrong (2.2 or 2.3 may have
> changed that)
No, pthreads changed that, from my understanding. linuxthreads did
it all in one thing w/o ever actually calling the kernel 'clone'. pthreads
properly calles 'clone' and therefore each thread gets it's own PID and as
such can be scheduled on any CPU. (Well, that's not the direct reason, but
you know what I mean).
> hmmm - when did that change - i know solarids has them run on multiple
> cpu's though...
Solaris implemented it kernel-level to begin with. The first
threading in Linux was done all in user-space, IIRC. Which meant that it
couldn't because a single process (to the kernel) won't get multiple CPUs.
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/