Linked by Thom Holwerda on Tue 26th Sep 2006 23:14 UTC
Intel Quad-core processors are only the beginning of what a revitalized Intel has to offer, the company's top executives said here Sept. 26. The chip maker will deliver in November its first quad-core processors - chips that incorporate four processors each - for both desktops and servers, said CEO Paul Otellini here, in an opening keynote speech at the Intel Developer Forum. The quad-core chips themselves will offer up to 70 percent greater performance in desktops and 50 percent in servers.
Permalink for comment 166336
To read all comments associated with this story, please click here.
RE[3]: The beginning of what?
by phoudoin on Thu 28th Sep 2006 08:31 UTC in reply to "RE[2]: The beginning of what?"
phoudoin
Member since:
2006-06-09

I seem to understand that its own GUI/window manager was heavily threaded, and that its API encouraged multithreaded development in frontends.
But regarding the CPU intensive parts of a program not written in any OS-specific special manner (let's say the Gecko renderer, or the filters in GIMP) is there anything that BeOS does that is more SMP-friendly than other OSes?


Not only BeOS's window manager was heavily threaded, but pretty much everything in BeOS is, from top to bottom. In 1990's, it was not that common. For example, all drivers and kernel modules, file systems included, must be SMP-aware (no giant lock) and many of them even use extra threads to achieve better/smoother asynchronous I/O handling.
Kernel is fully thread-safe and use also threads itself. The BONE network stack use threading everywhere.

And, indeed, all userland servers and their corresponding libraries (BeOS "kits", aka C++ API) are threaded. BeOS kits not only encouraged multithreaded development but in the case of GUI, its enforced on the developer.

Which, in 1990's, unfortunatly, didn't help this IMHO great operating system to get quickly the critical mass of graphical software ported from unix or windows code base. At this time, before SMP became mainstream, multithreaded development and parallel software programming was not that well mastered by developers. Since, things have improved. Alas, Be Inc. was too early too small to survive during these years.

Beside this pervasive threading model, BeOS have no other "exotic" SMP features.

Reply Parent Score: 1