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$

66 CHAPTER 5. PARTITIONING AND SYNCHRONIZATION DESIGN5.5 Performance Summary@@@ summarize performance of the various options.Forward-reference to the RCU/NBS section.
Chapter 6LockingTheroleofvillaininmuchofthepastfewdecades’concurrency research literature is played by locking,which stands accused of promoting deadlocks,convoying, starvation, unfairness, data races, andall manner of other concurrency sins. Interestinglyenough, theroleofworkhorseinshared-memoryparallelsoftware is played by, you guessed it, locking.There are a number of reasons behind this dichotomy:1. Many of locking’s sins have pragmatic designsolutions that work well in most cases, for example:(a) Lock hierarchies to avoid deadlock.(b) Deadlock-detection tools.(c) Locking-friendly data structures, such asarrays, hash tables, and radix trees.2. <strong>So</strong>me of locking’s sins are problems only athigh levels of contention, levels that are usuallyreached only by poorly designed programs.3. <strong>So</strong>me of locking’s sins are avoided by usingother synchronization mechanisms in concertwith locking, such as reference counters, statisticalcounters, simple non-blocking data structures,and RCU.4. Until quite recently, almost all large sharedmemoryparallelprogramsweredevelopedinsecret,so that it was difficult for most researchersto learn of these pragmatic solutions.5. All good stories need a villain, and lockinghas a long and honorable history serving as aresearch-paper whipping boy.This chapter will give an overview of a number ofways to avoid locking’s more serious sins.6.1 Staying AliveGiven that locking stands accused of deadlockand starvation, one important concern for sharedmemoryparallel developers is simply staying alive.The following sections therefore cover deadlock, livelock,starvation, unfairness, and inefficiency.6.1.1 Deadlock6.1.2 Livelock6.1.3 Starvation6.1.4 Unfairness6.1.5 Inefficiency6.2 Types of Locks6.2.1 Exclusive Locks6.2.2 Reader-Writer Locks6.2.3 Beyond Reader-Writer LocksSequence locks. VAXCluster six-state locking.6.2.4 While WaitingSpinlocks, sleeplocks, spin-sleeplocks (maybe), conditionallocking.6.2.5 Sleeping Safely6.3 Lock-Based ExistenceGuaranteesA key challenge in parallel programming is to provideexistence guarantees [GKAS99], so that attemptsto delete an object that others are concurrentlyattempting to access are correctly resolved.
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 54 and 55: 42 CHAPTER 4. COUNTING1 #define THE
Page 58 and 59: 46 CHAPTER 4. COUNTINGReadsAlgorith
Page 60 and 61: 48 CHAPTER 5. PARTITIONING AND SYNC
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 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 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:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
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 352 and 353:
340 BIBLIOGRAPHY[McK06] Paul E. McK
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?

Create successful ePaper yourself

Delete template?

Save as template?