RE: RasterMan on linux and threads

David Schwartz (davids@webmaster.com)
Fri, 17 Dec 1999 14:27:38 -0800

> 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)

You are entirely wrong.

In fact, running multiple threads on different processors has major cache
benefits. Your I/O code and your processing code may not fit in the L2 cache
at the same time, but one might fit in one processor's L2 cache while the
other fits in another's.

The caches have no difficuties at all with shared data. The cache coherency
protocol allows the same byte of data to be cached by more than one
processor at a time.

DS

-
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/