Linked by Thom Holwerda on Sun 10th Jul 2011 18:50 UTC, submitted by moondevil
Microsoft "The Microsoft and ETH Zurich research teams have published the source code of Barrelfish, a multikernel operating system for the multicore heterogeneous hardware of the future. Today's operating systems have been adapted to work on multiprocessor and multicore hardware, but they were not initially designed with multicore in mind, and they are not ready for heterogeneous hardware with hundreds of cores that is to come in the following ten years. The main problem is the concept of shared-memory and the contention arising from accessing the same data protected by locks. This is the problem that Barrelfish wants to address."
Permalink for comment 480281
To read all comments associated with this story, please click here.
RE[3]: Worthwhile?
by AndrewZ on Mon 11th Jul 2011 16:43 UTC in reply to "RE[2]: Worthwhile?"
AndrewZ
Member since:
2005-11-15

That feature would be trivially doable on just about any OS, the way it works in BeOS/Haiku isn't by actually physically disabling the CPU, it simply tells the scheduler to not schedule anything other than the idle thread on it (until one marks that CPU as enabled again in Pulse or ProcessController) ; the CPU is still very much active.


Thanks for correcting my misconception, interesting to know. If you were going to trivially code that in Windows, what would the code look like? Just curious.

Edited 2011-07-11 16:44 UTC

Reply Parent Score: 2