Difference between revisions of "CSC352 DT's Class Notes 2013"
| Line 68: | Line 68: | ||
** conclusion | ** conclusion | ||
* probably cover 1st section w/ dwarfs, plus conclusion, although everything is good | * probably cover 1st section w/ dwarfs, plus conclusion, although everything is good | ||
| − | |||
* General introduction to world of // computing in 2006 | * General introduction to world of // computing in 2006 | ||
| − | * old wisdom/new wisdom ==> world of // computing is changing | + | * old wisdom/new wisdom ==> '''world of // computing is changing''' |
* moore's law | * moore's law | ||
:::"Key to this approach is a layer of libraries and programming frameworks centered on the 13 computational bottlenecks ("dwarfs") that we identified in the original Berkeley View report. " | :::"Key to this approach is a layer of libraries and programming frameworks centered on the 13 computational bottlenecks ("dwarfs") that we identified in the original Berkeley View report. " | ||
* '''A dwarf is a class of algorithms that tend to have a common pattern of communication and computation'''. Dwarfs are well-defined targets from algorithmic, software, and architecture stand point. | * '''A dwarf is a class of algorithms that tend to have a common pattern of communication and computation'''. Dwarfs are well-defined targets from algorithmic, software, and architecture stand point. | ||
| − | + | * Page 3: multicore is not the answer. Manycore is. | |
| + | * High Performance Computing has good ideas and good solutions that map well to current parallel solutions==>use their solutions! | ||
* Page 7: we have been concentrating on massively parallel architectures, but this may apply to new forms of parallelism | * Page 7: we have been concentrating on massively parallel architectures, but this may apply to new forms of parallelism | ||
* Page 7: good match between scientific // approaches and current parallel (non scientific) domains | * Page 7: good match between scientific // approaches and current parallel (non scientific) domains | ||
* Page 7: 7 Dwarfs | * Page 7: 7 Dwarfs | ||
** ==> question: what's a dwarf? (google berkeley + dwarf) | ** ==> question: what's a dwarf? (google berkeley + dwarf) | ||
| + | ** Dwarfs replace benchmarking in a way | ||
** high level of abstraction | ** high level of abstraction | ||
| + | * '''The word is a new unit of information''' | ||
* Page 11: 3 new areas for adoption as dwarf? | * Page 11: 3 new areas for adoption as dwarf? | ||
** machine learning | ** machine learning | ||
| Line 86: | Line 88: | ||
** computer graphics | ** computer graphics | ||
* Page 14: introduces 6 new dwarfs | * Page 14: introduces 6 new dwarfs | ||
| + | * Intel has similar breakdown of paradigms that it calls RMS: Recognition, Mining, and Synthesis. | ||
| + | * '''A parallel to be made: IBM 360 and microprocessors. Now multicore can benefit from High Performance Computing''' | ||
* Page 19: End of software Dwarf section ==> Good place to break | * Page 19: End of software Dwarf section ==> Good place to break | ||
* Page 20: beginning of hardware | * Page 20: beginning of hardware | ||
| Line 92: | Line 96: | ||
** network | ** network | ||
* Page 32: Programming models | * Page 32: Programming models | ||
| + | * Need a new type: '''Unicode''' (words and unicode are important units/types to support!) | ||
** Does not include threading | ** Does not include threading | ||
** MPI | ** MPI | ||
** Map-REduce | ** Map-REduce | ||
* Page 36: system software | * Page 36: system software | ||
| − | ** '''Autotuner''' | + | ** '''Autotuner''': compilers are not good enough. Parallel programming is so hard, that we should have machines try out all possible optimizations and figure out how to make it work best. |
| + | |||
* Page 40: virtual machines to the rescue | * Page 40: virtual machines to the rescue | ||
* Page 44: conclusion | * Page 44: conclusion | ||
