Our Pattern Language is a paper defining patterns used during parallel programming. Different patterns are grouped into different categories: the interrelated architectural and computational patterns, parallel strategy, implementation strategy and concurrent execution patterns.
I thought their division was reasonable. While the paper lacks depth on describing each pattern, other papers can give the details of why and when to use each pattern. This paper tackles the problem of why they are needed at all and to facilitate communication between people working on parallel programs. When the language is defined, less confusion of terms occurs.
As parallelism becomes more prevalent with multiple cores in each CPU, programmers need to learn to take advantage of it. The problem is not so much in the tools available to develop with, but in educating programmers on how to design programs to take advantage of the parallelism. Knowing that these patterns exist for creating such programs is half the battle, and this paper helps on that front.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment