The motivation that Andrew provides for cocurrency makes a lot of sense.. As we move toward more cores/chip then it seems obvious we need concurrency.
We also need it for networks and things like Amazon's EC2. So see Starfish, which I think is relevant ... though I must admit I am far from certain ;) http://www.usenix.org/events/usenix03/tech/freenix03/gabber/gabber_html/paper.html It also seems obvious to me that many programmers should not need to care about this any more than they need to care about how the compiler generates code. Simple example. Say I have loop that runs for M times. Say I have N cores. Why not have the complier generate the code (including managing memory) to run N loop instances and thus run in approoximately 1/N the time? So time to run goes from M to M/N mas o menos. Loops are pretty common so this naive idea could go a long way ... Then one simply trys to get programmers to think of programs as loops, something they find easy to do. Huh? BobLQ -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
