Is Parallel Programming Hard, And, If So, What Can You Do About It?

More documents

Recommendations

Info

$TeX op Mac OS X, met teTeX en TeXShop - Nluug$

340 BIBLIOGRAPHY[McK06] Paul E. McKenney. SleepableRCU. Available: http://lwn.net/Articles/202847/ Revised:http://www.rdrop.com/users/paulmck/RCU/srcu.2007.01.14a.pdf[Viewed August 21, 2006], October2006.[McK07a] Paul E. McKenney. The design of preemptibleread-copy-update. Available:http://lwn.net/Articles/253651/[Viewed October 25, 2007], October2007.[McK07b] Paul E. McKenney. [PATCH] QRCUwithlocklessfastpath. Available: http://lkml.org/lkml/2007/2/25/18[Viewed March 27, 2008], February2007.[McK07c] Paul E. McKenney. [patch rfc 0/9]RCU: Preemptible RCU. Available:http://lkml.org/lkml/2007/9/10/213 [Viewed October 25, 2007],September 2007.[McK07d] Paul E. McKenney. PriorityboostingRCU read-side criticalsections. Available: http://lwn.net/Articles/220677/ Revised:http://www.rdrop.com/users/paulmck/RCU/RCUbooststate.2007.04.16a.pdf [Viewed September 7,2007], February 2007.[McK07e] Paul E. McKenney. RCU andunloadable modules. Available:http://lwn.net/Articles/217484/[Viewed November 22, 2007], January2007.[McK07f] Paul E. McKenney. Using Promelaand Spin to verify parallel algorithms.Available: http://lwn.net/Articles/243851/ [Viewed September8, 2007], August 2007.[McK07g] Paul E. McKenney. What is RCU?Available: http://www.rdrop.com/users/paulmck/RCU/whatisRCU.html[Viewed July 6, 2007], 07 2007.[McK08a] Paul E. McKenney. HierarchicalRCU. Available: http://lwn.net/Articles/305782/ [Viewed November6, 2008], November 2008.[McK08b] Paul E. McKenney. RCU part 3: theRCU API. Available: http://lwn.net/Articles/264090/ [Viewed January10, 2008], January 2008.[McK08c] Paul E. McKenney. What is RCU? part2: Usage. Available: http://lwn.net/Articles/263130/ [Viewed January 4,2008], January 2008.[McK09a] Paul E. McKenney. Re: [patch fyi]rcu: the bloatwatch edition. Available:http://lkml.org/lkml/2009/1/14/449 [Viewed January 15, 2009],January 2009.[McK09b] Paul E. McKenney. Transactionalmemory everywhere?http://paulmck.livejournal.com/tag/transactional%20memory%20everywhere, September 2009.[MD92]Paul E. McKenney and Ken F. Dove.Efficientdemultiplexingofincomingtcppackets. In SIGCOMM ’92, Proceedingsof the Conference on CommunicationsArchitecture & Protocols, pages269–279, Baltimore, MD, August 1992.Association for Computing Machinery.[Mel06] Melbourne School of Engineering.CSIRAC. Available:http://www.csse.unimelb.edu.au/dept/about/csirac/ [Viewed:December 7, 2008], 2006.[Met99][MG92]Panagiotis Takis Metaxas. Fast ditheringon a data-parallel computer. InProceedings of the IASTED InternationalConference on Parallel and DistributedComputing and Systems, pages570–576, Cambridge, MA, USA, 1999.IASTED.Paul E. McKenney and Gary Graunke.Efficient buffer allocation on sharedmemorymultiprocessors. In IEEEWorkshop on the Architecture andImplementation of High PerformanceCommunication Subsystems, pages194–199, Tucson, AZ, February 1992.The Institute of Electrical and ElectronicsEngineers, Inc.[MGM + 09] Paul E. McKenney, Manish Gupta,Maged M. Michael, Phil Howard,JoshuaTriplett, and Jonathan Walpole.
BIBLIOGRAPHY 341[Mic04]Is parallel programming hard, andif so, why? Technical ReportTR-09-02, Portland State University,Portland, OR, USA, February 2009.Available: http://www.cs.pdx.edu/pdfs/tr0902.pdf [Viewed February19, 2009].Maged M. Michael. Hazard pointers:Safe memory reclamation for lock-freeobjects. IEEE Transactions on Paralleland Distributed Systems, 15(6):491–504, June 2004.[MK88] MarshallKirkMcKusickandMichael J.Karels. Design of a general purposememory allocator for the 4.3BSD UNIXkernel. InUSENIX Conference Proceedings,Berkeley CA, June 1988.[MM00]Ingo Molnar and David S. Miller.brlock. Available: http://www.tm.kernel.org/pub/linux/kernel/v2.3/patch-html/patch-2.3.49/linux_include_linux_brlock.h.html[Viewed September 3, 2004], March2000.[MMW07] Paul E. McKenney, Maged Michael,and Jonathan Walpole. Why the grassmay not be greener on the other side: Acomparison of locking vs. transactionalmemory. In Programming Languagesand Operating Systems, pages 1–5, NewYork, NY, USA, October 2007. ACMSIGOPS.[Mol05] Ingo Molnar. Index of/pub/linux/kernel/projects/rt. Available:http://www.kernel.org/pub/linux/kernel/projects/rt/ [ViewedFebruary 15, 2005], February 2005.[Moo03] Gordon Moore. No exponential isforever–but we can delay forever. InIBM Academy of Technology 2003 AnnualMeeting, San Francisco, CA, October2003.[MPA + 06] Paul E. McKenney, Chris Purcell,Algae, Ben Schumin, Gaius Cornelius,Qwertyus, Neil Conway, Sbw, Blainster,Canis Rufus, Zoicon5, Anome,and Hal Eisen. Read-copy update.Available: http://en.wikipedia.org/wiki/Read-copy-update [ViewedAugust 21, 2006], July 2006.[MPI08][MR08][MS93][MS98][MS05][MS08][MS09][MSK01]MPI Forum. Message passing interfaceforum. Available: http://www.mpi-forum.org/ [Viewed September 9,2008], September 2008.Paul E. McKenney and Steven Rostedt.Integrating and validating dynticksand preemptable rcu. Available:http://lwn.net/Articles/279077/[Viewed April 24, 2008], April 2008.Paul E. McKenney and Jack Slingwine.Efficient kernel memory allocation onshared-memory multiprocessors. InUSENIX Conference Proceedings, pages295–306, Berkeley CA, February 1993.USENIX Association. Available: http://www.rdrop.com/users/paulmck/scalability/paper/mpalloc.pdf[Viewed January 30, 2005].Paul E. McKenney and John D. Slingwine.Read-copy update: Using executionhistory to solve concurrency problems.In Parallel and Distributed Computingand Systems, pages 509–518,Las Vegas, NV, October 1998. Available:http://www.rdrop.com/users/paulmck/RCU/rclockpdcsproof.pdf[Viewed December 3, 2007].Paul E. McKenney and DipankarSarma. Towards hard realtime responsefrom the Linux kernel on SMP hardware.In linux.conf.au 2005, Canberra,Australia, April 2005. Available: http://www.rdrop.com/users/paulmck/RCU/realtimeRCU.2005.04.23a.pdf[Viewed May 13, 2005].MySQL AB and Sun Microsystems.MySQL Downloads. Available:http://dev.mysql.com/downloads/[Viewed November 26, 2008], November2008.Paul E. McKenney and Raul Silvera.Example power implementationfor c/c++ memory model.Available: http://www.rdrop.com/users/paulmck/scalability/paper/N2745r.2009.02.27a.html [Viewed:April 5, 2009], February 2009.Paul E. McKenney, Jack Slingwine, andPhil Krueger. Experience with an efficientparallel kernel memory alloca-
Page 1 and 2:
Is Parallel Programming Hard, And,
Page 3 and 4:
Contents1 Introduction 11.1 Histori
Page 5 and 6:
CONTENTSv6 Locking 676.1 Staying Al
Page 7 and 8:
CONTENTSviiB Synchronization Primit
Page 9 and 10:
CONTENTSixE.7.1 Introduction to Pre
Page 11 and 12:
PrefaceThe purpose of this book is
Page 13 and 14:
Chapter 1IntroductionParallel progr
Page 15 and 16:
1.2. PARALLEL PROGRAMMING GOALS 3CP
Page 17 and 18:
1.3. ALTERNATIVES TO PARALLEL PROGR
Page 19 and 20:
1.4. WHAT MAKES PARALLEL PROGRAMMIN
Page 21 and 22:
1.5. GUIDE TO THIS BOOK 9other hand
Page 23 and 24:
Chapter 2Hardware and its HabitsMos
Page 25:
2.1. OVERVIEW 13Therefore, as shown
Page 28 and 29:
16 CHAPTER 2. HARDWARE AND ITS HABI
Page 30 and 31:
18 CHAPTER 2. HARDWARE AND ITS HABI
Page 32 and 33:
20 CHAPTER 3. TOOLS OF THE TRADE1 p
Page 34 and 35:
22 CHAPTER 3. TOOLS OF THE TRADE1 p
Page 36 and 37:
24 CHAPTER 3. TOOLS OF THE TRADE1.1
Page 38 and 39:
26 CHAPTER 3. TOOLS OF THE TRADEQui
Page 40 and 41:
28 CHAPTER 3. TOOLS OF THE TRADE
Page 42 and 43:
30 CHAPTER 4. COUNTING1 atomic_t co
Page 44 and 45:
32 CHAPTER 4. COUNTING4.2.3 Eventua
Page 46 and 47:
34 CHAPTER 4. COUNTINGvanish when t
Page 48 and 49:
36 CHAPTER 4. COUNTINGper-thread va
Page 50 and 51:
38 CHAPTER 4. COUNTING1 unsigned lo
Page 52 and 53:
Page 54 and 55:
42 CHAPTER 4. COUNTING1 #define THE
Page 56 and 57:
Page 58 and 59:
46 CHAPTER 4. COUNTINGReadsAlgorith
Page 60 and 61:
48 CHAPTER 5. PARTITIONING AND SYNC
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
68 CHAPTER 6. LOCKING1 int delete(i
Page 82 and 83:
70 CHAPTER 7. DATA OWNERSHIP
Page 84 and 85:
72 CHAPTER 8. DEFERRED PROCESSINGfo
Page 86 and 87:
74 CHAPTER 8. DEFERRED PROCESSINGth
Page 88 and 89:
76 CHAPTER 8. DEFERRED PROCESSING
Page 90 and 91:
78 CHAPTER 8. DEFERRED PROCESSINGfi
Page 92 and 93:
80 CHAPTER 8. DEFERRED PROCESSINGti
Page 94 and 95:
82 CHAPTER 8. DEFERRED PROCESSINGNo
Page 96 and 97:
84 CHAPTER 8. DEFERRED PROCESSING12
Page 98 and 99:
Page 100 and 101:
88 CHAPTER 8. DEFERRED PROCESSINGvo
Page 102 and 103:
90 CHAPTER 8. DEFERRED PROCESSINGLi
Page 104 and 105:
92 CHAPTER 8. DEFERRED PROCESSINGpe
Page 106 and 107:
94 CHAPTER 8. DEFERRED PROCESSINGCa
Page 108 and 109:
96 CHAPTER 8. DEFERRED PROCESSINGTh
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
104 CHAPTER 8. DEFERRED PROCESSINGs
Page 118 and 119:
106 CHAPTER 8. DEFERRED PROCESSINGo
Page 120 and 121:
108 CHAPTER 8. DEFERRED PROCESSING
Page 122 and 123:
110 CHAPTER 9. APPLYING RCU1 struct
Page 124 and 125:
112 CHAPTER 9. APPLYING RCU
Page 126 and 127:
114 CHAPTER 10. VALIDATION: DEBUGGI
Page 128 and 129:
116 CHAPTER 11. DATA STRUCTURES
Page 130 and 131:
118 CHAPTER 12. ADVANCED SYNCHRONIZ
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
138 CHAPTER 13. EASE OF USEFigure 1
Page 152 and 153:
140 CHAPTER 13. EASE OF USE
Page 154 and 155:
142 CHAPTER 14. TIME MANAGEMENT
Page 156 and 157:
144 CHAPTER 15. CONFLICTING VISIONS
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
154 APPENDIX A. IMPORTANT QUESTIONS
Page 168 and 169:
156 APPENDIX A. IMPORTANT QUESTIONS
Page 170 and 171:
158 APPENDIX B. SYNCHRONIZATION PRI
Page 172 and 173:
160 APPENDIX B. SYNCHRONIZATION PRI
Page 174 and 175:
162 APPENDIX C. WHY MEMORY BARRIERS
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
184 APPENDIX D. READ-COPY UPDATE IM
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
244 APPENDIX E. FORMAL VERIFICATION
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
272 APPENDIX F. ANSWERS TO QUICK QU
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303: 290 APPENDIX F. ANSWERS TO QUICK QU
Page 342 and 343: 330 APPENDIX G. GLOSSARY(2) A physi
Page 344 and 345: 332 APPENDIX G. GLOSSARYnear by. Th
Page 346 and 347: 334 APPENDIX G. GLOSSARY
Page 348 and 349: 336 BIBLIOGRAPHY[But97]USA, March 2
Page 350 and 351: 338 BIBLIOGRAPHY[HMB06][Hol03][HP95
Page 354 and 355: 342 BIBLIOGRAPHYtor. Software - Pra
Page 356 and 357: 344 BIBLIOGRAPHY[UoC08][VGS08]Berke
Page 358: 346 APPENDIX H. CREDITSH.4 Original
show all

Is Parallel Programming Hard, And, If So, What Can You Do About It?

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?