[...] > I've got the research paper somewhere, but I believe > the results are > pretty much as described - it got slower because it > added the overhead > of everything waiting on the lock to the frame > buffer. [...] > But retrofitting a 25-year old multi-million line > code base to be completely > thread-safe, much less thread-hot, is not a small > task. And since we already > have GPU's that run 128 or 256 operations in parallel > without adding > any threads to the core server, it's not clear what > the effects would be. > > That's not to say X is ignoring the multi-core > revolution completely. > The XCB API that's slowly replacing Xlib as the base > of the client side of > the graphics stack was designed from the ground up > for much better > concurrency support, as well as much more flexible > latency handling. [...]
Interesting as always! Thanks... -- This message posted from opensolaris.org _______________________________________________ xwin-discuss mailing list [email protected] List info: http://mail.opensolaris.org/mailman/listinfo/xwin-discuss Unsubscribe: http://mail.opensolaris.org/mailman/options/xwin-discuss
