> If libthread is able to grab real processors per thread and get them > scheduled, one's concurrent style code ultimately ends up having potential > to run in parallel on those cores/processors.
due to the specific meaning of "thread" in the thread library, this statement is misleading. only procs may run in parallel. threads are scheduled cooperatively. since procs are scheduled by the kernel, the kernel is responsible for scheduling procs; the thread library doesn't grab processors. - erik
