BookOutline: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
* The scope of the VTK-m: what it does, why it is useful | * The scope of the VTK-m: what it does, why it is useful | ||
Dependencies: last chapter written | Dependencies: last chapter written (or at least all other chapters should be taking shape) | ||
Authors: Hank and Ken | Authors: Hank and Ken | ||
Revision as of 18:49, 6 August 2015
Book title: Achieving Portable Performance For Visualization, Using VTK-m
The book is organized into two parts:
- Concepts in Portable Performance and Modern Architectures
- The VTK-m Approach
Each chapter has dependencies listed. A dependency for chapter C1 on chapter C2 means that C2 should be complete (or in reasonable shape) before C1 is started, so that the terminology can be consistent.
Introduction Chapter
Chapter 0: Introduction
- The Organization of this Book
- The scope of the VTK-m: what it does, why it is useful
Dependencies: last chapter written (or at least all other chapters should be taking shape)
Authors: Hank and Ken
Concepts in Portable Performance and Modern Architectures
Chapter 1.1: Revolutions in Processor Architectures
Topics:
- threading vs vector / multi-core/many-core / host-device / memory hierarchies
- historical discussion: Moore’s law, but Dinar scaling failed … how to deal with extra transistor
- exascale power story, state of current Top500
Dependencies: none
Chapter 1.2: GPU
Dependencies: Chapter 1.1
Experts: Tom Fogal?
Chapter 1.3: Xeon Phi
Dependencies: Chapter 1.1
Experts: James Reinders of Intel said he would participate