Parallelism shift and programming

I've just finished my master's thesis which covers the shift to parallelism. It is focused on desktop programming but most of the problems are shared with embedded programming. I'd very much like to get some comments and perhaps have some discussions on what I've written.

If it sounds interesting, you can find the thesis at Johan's place on the web

Part 2 of the thesis, which covers C++'s new memory model, is probably not that interesting to most of you.

Best Regards, Johan Torp

--- ABSTRACT ---
Part 1 - A bird's eye view of desktop parallelism,
Part 2 - Zooming in on C++0x's memory model

The first part of the thesis is an overview of the paradigmatic shift to parallelism that is currently taking place. It explains why processors need to become parallel, how they might function and which types of parallelism there are. Given that information, it explains why threads and locks is not a suitable programming model and how threading is being improved and used to extract parallel performance. It also covers the problems that await new parallel programming models and how they might work. The final chapter surveys the landscape of existing parallel software and hardware projects and relates them to the overview. The overview is intended for programmers and architects of desktop and embedded systems.

The second part explains how to use C++'s upcoming memory model and atomic API. It also relates the memory model to classical definitions of distributed computing in an attempt to bridge the gap in terminology between the research literature and C++. An implementation of hazard pointers and a lock-free stack and queue are given as example C++0x code. This part is aimed at expert C++ developers and the research community.

Edited by John, 29 September 2008 - 11:27 AM.
fixed the link