Linked by Thom Holwerda on Fri 19th Mar 2010 13:00 UTC, submitted by Jim Lynch
Permalink for comment 414499
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2005-07-06
To clarify my previous point, the article is abut scaling beyond the relatively small numbers of cores we have now and going into the so called "many-core" area.
The hardware is also likely to end up quite different from what we have now. Today the systems are kept in sync by cache coherence, however this itself has scaling problems so in the future we'll see non cache-coherent systems, Intel's single chip cloud is an example.
Desktop OSs simply aren't designed for this sort of design and
as DragonFly BSD is the only one I'm aware of working on this for the desktop/small server. There are other OSs but they are big iron or research OSs (e.g. Barrelfish).
Interestingly BeOS/Haiku does have one of the key elements in place already - the API uses message passing. So it's probably a lot better placed for future systems than most OSs.
What would be really interesting is if you were to combine the DragonFly kernel with the Haiku user land. That'd give you a highly scalable, truly desktop OS.