> thqats what i was lead to believe - for all practical purposes if you
> have a api library that goes and for short bursts creates and destroys
> threads to try and speedup a chrunching-heavy inner loop by spliting
> it into segments and having different threads handle each segment -
> then it wont get scheduled across multiple processors - if this is he
> case si there a way to force it (so i can at lats get benchmarks as i
> can pretty much be sure it ont give any speedup on a UP box)
If the bursts are short enough, it will be more work to
load the data into cache on another CPU than to do the
calculations 'locally'.
When it doesn't make sense to move the work to another
CPU, it won't make sense to force it there. OTOH, when
the amount of work is big enough, it _will_ get run on
multiple CPUs in parrallel.
regards,
Rik
-- The Internet is not a network of computers. It is a network of people. That is its real strength.
- 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/