|
|
| (8 intermediate revisions by the same user not shown) |
| Line 4: |
Line 4: |
| | __TOC__ | | __TOC__ |
| | | | |
| | + | <br /> |
| | + | <center> |
| | + | '''PLEASE SEE [[CSC352_2017_DT%27s_Notes| THE 2017 NOTES PAGE FOR MORE INFO]]''' |
| | + | </center> |
| | + | <br /> |
| | ==Threads== | | ==Threads== |
| | * good example with multiple ping processes: [http://www.wellho.net/solutions/python-python-threads-a-first-example.html] | | * good example with multiple ping processes: [http://www.wellho.net/solutions/python-python-threads-a-first-example.html] |
| Line 11: |
Line 16: |
| | * [[NQueens.py | NQueens.py]] | | * [[NQueens.py | NQueens.py]] |
| | * [[threadedNQueens.py | threadedNQueens.py ]] | | * [[threadedNQueens.py | threadedNQueens.py ]] |
| | + | * [[classExample1.py | classExample1.py ]] |
| | + | * [[classExample2.py | classExample2.py ]] |
| | + | * [[classExample3.py | classExample3.py ]] |
| | * [[serialPing.py | serialPing.py ]] | | * [[serialPing.py | serialPing.py ]] |
| | * [[threadedPing.py | threadedPing.py ]] | | * [[threadedPing.py | threadedPing.py ]] |
| Line 56: |
Line 64: |
| | | | |
| | ==Papers== | | ==Papers== |
| − | ===Landscape of parallel computing research: a view from berkeley===
| |
| − | ----
| |
| − | * good intro paper.
| |
| − | * 3 sections
| |
| − | ** software
| |
| − | ** hardware
| |
| − | ** performance/programming models
| |
| − | ** conclusion
| |
| − | * probably cover 1st section w/ dwarfs, plus conclusion, although everything is good
| |
| − | ----
| |
| − | * General introduction to world of // computing in 2006
| |
| − | * old wisdom/new wisdom ==> world of // computing is changing
| |
| − | * 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. "
| |
| − | * 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: 7 Dwarfs
| |
| − | ** ==> question: what's a dwarf? (google berkeley + dwarf)
| |
| − | ** high level of abstraction
| |
| − | * Page 11: 3 new areas for adoption as dwarf?
| |
| − | ** machine learning
| |
| − | ** database software
| |
| − | *** Page 12: map-reduce
| |
| − | ** computer graphics
| |
| − | * Page 14: introduces 6 new dwarfs
| |
| − | * Page 19: End of software Dwarf section ==> Good place to break
| |
| − | * Page 20: beginning of hardware
| |
| − | ** processor
| |
| − | ** memory
| |
| − | ** network
| |
| − | * Page 32: Programming models
| |
| − | ** Does not include threading
| |
| − | ** MPI
| |
| − | ** Map-REduce
| |
| − | * Page 36: system software
| |
| − | ** '''Autotuner'''
| |
| − | * Page 40: virtual machines to the rescue
| |
| − | * Page 44: conclusion
| |
| − |
| |
| − |
| |
| − |
| |
| | | | |
| | + | [[CSC352 Notes on A View From Berkeley| Notes]] on a View from Berkeley paper |
| | | | |
| | | | |
| | </onlydft> | | </onlydft> |
| | + | [[Category:CSC352]][[Category:Class Notes]] |
