Concurrent Programming on Windows

by Duffy, Joe

• ISBN13: 9780321434821
• ISBN10: 032143482X
• Edition: 1st
• Format: Paperback
• Copyright: 2008-10-28
• Publisher: Addison-Wesley Professional

Summary

"When you begin using multi-threading throughout an application, the importance of clean architecture and design is critical. . . . This places an emphasis on understanding not only the platformrs"s capabilities but also emerging best practices. Joe does a great job interspersing best practices alongside theory throughout his book." From the Foreword by Craig Mundie, Chief Research and Strategy Officer, Microsoft Corporation Author Joe Duffy has risen to the challenge of explaining how to write software that takes full advantage of concurrency and hardware parallelism. InConcurrent Programming on Windows,he explains how to design, implement, and maintain large-scale concurrent programs, primarily using C# and C++ for Windows. Duffy aims to give application, system, and library developers the tools and techniques needed to write efficient, safe code for multicore processors. This is important not only for the kinds of problems where concurrency is inherent and easily exploitable-such as server applications, compute-intensive image manipulation, financial analysis, simulations, and AI algorithms-but also for problems that can be speeded up using parallelism but require more effort-such as math libraries, sort routines, report generation, XML manipulation, and stream processing algorithms. Concurrent Programming on Windowshas four major sections: The first introduces concurrency at a high level, followed by a section that focuses on the fundamental platform features, inner workings, and API details. Next, there is a section that describes common patterns, best practices, algorithms, and data structures that emerge while writing concurrent software. The final section covers many of the common system-wide architectural and process concerns of concurrent programming. This is theonlybook yours"ll need in order to learn the best practices and common patterns for programming with concurrency on Windows and .NET.

Author Biography

Joe Duffy is the development lead, architect, and founder of the Parallel Extensions to the .NET Framework team at Microsoft. In addition to hacking code and managing a team of developers, he works on long-term vision and incubation efforts, such as language and type system support for concurrency safety. He previously worked on the Common Language Runtime team. Joe blogs regularly at www.bluebytesoftware.com/blog.

Table of Contents

Foreword	p. xix
Preface	p. xxiii
Acknowledgments	p. xxvii
About the Author	p. xxix
Concepts	p. 1
Introduction	p. 3
Why Concurrency?	p. 3
Program Architecture and Concurrency	p. 6
Layers of Parallelism	p. 8
Why Not Concurrency?	p. 10
Where Are We?	p. 11
Synchronization and Time	p. 13
Managing Program State	p. 14
Synchronization: Kinds and Techniques	p. 38
Where Are We?	p. 73
Mechanisms	p. 77
Threads	p. 79
Threading from 10,001 Feet	p. 80
The Life and Death of Threads	p. 89
Where Are We?	p. 124
Advanced Threads	p. 127
Thread State	p. 127
Inside Thread Creation and Termination	p. 152
Thread Scheduling	p. 154
Where Are We?	p. 180
Windows Kernel Synchronization	p. 183
The Basics: Signaling and Waiting	p. 184
Using the Kernel Objects	p. 211
Where Are We?	p. 251
Data and Control Synchronization	p. 253
Mutual Exclusion	p. 255
Reader/Writer Locks (RWLs)	p. 287
Condition Variables	p. 304
Where Are We?	p. 312
Thread Pools	p. 315
Thread Pools 101	p. 316
Windows Thread Pools	p. 323
CLR Thread Pool	p. 364
Performance When Using the Thread Pools	p. 391
Where Are We?	p. 398
Asynchronous Programming Models	p. 399
Asynchronous Programming Model (APM)	p. 400
Event-Based Asynchronous Pattern	p. 421
Where Are We?	p. 427
Fibers	p. 429
An Overview of Fibers	p. 430
Using Fibers	p. 435
Additional Fiber-Related Topics	p. 445
Building a User-Mode Scheduler	p. 453
Where Are We?	p. 473
	p. 475
Memory Models and Lock Freedom	p. 477
Memory Load and Store Reordering	p. 478
Hardware Atomicity	p. 486
Memory Consistency Models	p. 506
Examples of Low-Lock Code	p. 520
Where Are We?	p. 541
Concurrency Hazards	p. 545
Correctness Hazards	p. 546
Liveness Hazards	p. 572
Where Are We?	p. 609
Parallel Containers	p. 613
Fine-Grained Locking	p. 616
Lock Free	p. 632
Table of Contents provided by Publisher. All Rights Reserved.

Excerpts

I began writing this book towards the end of 2005. At the time, dual-core processors were becoming standard on the mainstream PC's that ordinary (non-programmer) consumers were buying, and a small number of people in industry had begun to make noise about the impending concurrency problem. (Herb Sutter'sThe Free Lunch is Overpaper immediately comes to mind.) The problem people were worried about, of course, was that the software of the past was not written in a way that would allow it to naturally exploit that additional compute power. Contrast that with the never-ending increase in clock speeds. No more free lunchindeed.It seemed to me that concurrency was going to be an important part of every software developer's job somewhere down the road and that a book like this would be important and useful. Just over two years later, the impact is beginning to ripple up from the operating system, through the libraries, and on up to applications themselves.This was about the same time I had wrapped up prototyping a small side-project on which I had been burning the midnight oil for the previous six months:Parallel Language Integrated Query(PLINQ). The PLINQ project was a conduit for me to explore the intricacies of concurrency, multi-core, and specifically how parallelism might be used in real-world, everyday programs. I used it as a tool to figure out where the platform was lacking. This was in addition to spending my day job at Microsoft focused onsoftware transactional memory(STM), a technology that in the intervening two years has become somewhat of an industry buzzword. Needless to say, I had become pretty entrenched in all topics concurrency. What better way to get entrenched even further than to write a book on the subject?As I worked on all of these projects, and eventually PLINQ grew intoParallel Extensions to the .NET Framework,I was amazed at how few good books on Windows concurrency were available. I remember time and time again being astonished or amazed at some intricate and esoteric bit of concurrency-related information, jotting it down, and earmarking it for inclusion in this book. I onlywishedsomebody had written it down before me, so that I didn't need to scour it from numerous sources: hallway conversations, long nights of pouring over Windows and CLR source code, and reading and rereading countless Microsoft employee blogs. But the best books on the topic dated back to the early '90s and, while still really good, focused too much on the mechanics and not on how to structure parallel programs, implement parallel algorithms, deal with concurrency hazards, and other important concepts. Everything else targeted academics and researchers, and not application, system, and library developers.I set out to write a book that I'd have found fascinating and a useful way to shortcut all of the random bits of information I had to learn throughout. Although it took me a surprisingly long two-and-a-half years to finish this book (!), the state of the art has evolved slowly, and the state of good books on the topic hasn't changed much either. The result of my efforts, I hope, is a new book that is down-to-earth and useful, but still full of very deep technical information. It is for any Windows or .NET developer who believes that concurrency is going to be a fundamental requirement of all software somewhere down the road, as all industry trends seem to imply.I look forward to kicking back and enjoying this book. And I sincerely hope you do too. Book StructureI've structured the book into four major parts. The first,Concepts,introduces concurrency at a high level without going too deep into any one topic. The next part,Mechanisms,focuses squarely on the fundamental platform features, inner workings, and API details. After that, the part onTechniquesdescribes common patterns, best practices, algorithms, and data structu