book

PThreads Programming

by Dick Buttlar, Jacqueline Farrell, Bradford Nichols

September 1996

Intermediate to advanced

286 pages

7h 11m

English

O'Reilly Media, Inc.

Read now

Unlock full access

Pthreads Programming
A Note Regarding Supplemental Files
Examples
Preface
OrganizationExample ProgramsFTPTypographical ConventionsAcknowledgments
1. Why Threads?
What Are Pthreads?Potential ParallelismSpecifying Potential Parallelism in a Concurrent Programming EnvironmentUNIX Concurrent Programming: Multiple ProcessesCreating a new process: forkPthreads Concurrent Programming: Multiple ThreadsCreating a new thread: pthread_createThreads are peersParallel vs. Concurrent ProgrammingSynchronizationSharing Process ResourcesCommunicationSchedulingWho Am I? Who Are You?Terminating Thread ExecutionExit Status and Return ValuesPthreads Library Calls and ErrorsWhy Use Threads Over Processes?A Structured Programming EnvironmentChoosing Which Applications to Thread
2. Designing Threaded Programs
Suitable Tasks for ThreadingModelsBoss/Worker ModelPeer ModelPipeline ModelBuffering Data Between ThreadsSome Common ProblemsPerformanceExample: An ATM ServerThe Serial ATM ServerHandling asynchronous events: blocking with selectHandling file I/O: blocking with read/writeThe Multithreaded ATM ServerModel: boss/worker modelThe boss threadDynamically detaching a threadA worker threadSynchronization: what’s neededFuture enhancementsExample: A Matrix Multiplication ProgramThe Serial Matrix-Multiply ProgramThe Multithreaded Matrix-Multiply ProgramPassing data to a new threadSynchronization in the matrix-multiply program
3. Synchronizing Pthreads
Selecting the Right Synchronization ToolMutex VariablesUsing MutexesError Detection and Return ValuesUsing pthread_mutex_trylockWhen Other Tools Are BetterSome Shortcomings of MutexesContention for a MutexExample: Using Mutexes in a Linked ListComplex Data Structures and Lock GranularityRequirements and Goals for SynchronizationAccess Patterns and GranularityLocking HierarchiesSharing a Mutex Among ProcessesCondition VariablesUsing a Mutex with a Condition VariableWhen Many Threads Are WaitingChecking the Condition on Wake Up: Spurious Wake UpsCondition Variable AttributesCondition Variables and UNIX SignalsCondition Variables and CancellationReader/Writer LocksSynchronization in the ATM ServerSynchronizing Access to Account DataLimiting the Number of Worker ThreadsSynchronizing a Server ShutdownThread PoolsAn ATM Server Example That Uses a Thread PoolInitializing a thread poolChecking for workAdding workDeleting a thread poolAdapting the atm_server_init and main routines
4. Managing Pthreads
Setting Thread AttributesSetting a Thread’s Stack SizeSpecifying the Location of a Thread’s StackSetting a Thread’s Detached StateSetting Multiple AttributesDestroying a Thread Attribute ObjectThe pthread_once MechanismExample: The ATM Server’s Communication ModuleUsing a statically initialized mutexUsing the pthread_once mechanismKeys: Using Thread-Specific DataInitializing a Key: pthread_key_createAssociating Data with a KeyRetrieving Data from a KeyDestructorsCancellationThe Complication with CancellationCancelability Types and StatesCancellation Points: More on Deferred CancellationA Simple Cancellation ExampleThe bullet_proof thread: no effectThe ask_for_it thread: deferred cancellationThe sitting_duck thread: asynchronous cancellationCleanup StacksCancellation in the ATM ServerAborting a depositScheduling PthreadsScheduling Priority and PolicyScheduling Scope and Allocation DomainsRunnable and Blocked ThreadsScheduling PriorityScheduling PolicyUsing Priorities and PoliciesSetting Scheduling Policy and PriorityInheritanceScheduling in the ATM ServerMutex Scheduling AttributesPriority CeilingPriority InheritanceThe ATM Example and Priority Inversion
5. Pthreads and UNIX
Threads and SignalsTraditional Signal ProcessingSending signals and waiting for signalsUsing a signal mask to block signalsSignal Processing in a Multithreaded WorldSynchronously generated signalsAsynchronously generated signalsPer-thread signal masksPer-process signal actionsPutting it all togetherThreads in Signal HandlersA Simple ExampleSome Signal IssuesHandling Signals in the ATM ExampleThreadsafe Library Functions and System CallsThreadsafe and Reentrant FunctionsExample of Thread-Unsafe and Threadsafe Versions of the Same FunctionFunctions That Return Pointers to Static DataLibrary Use of errnoThe Pthreads Standard Specifies Which Functions Must Be ThreadsafeAlternative interfaces for functions that return static dataAdditional routines for performance considerationsFile-locking functions for threadsWhere are the threadsafe functions?Using Thread-Unsafe Functions in a Multithreaded ProgramCancellation-Safe Library Functions and System CallsAsynchronous Cancellation-Safe FunctionsCancellation Points in System and Library CallsThread-Blocking Library Functions and System CallsThreads and Process ManagementCalling fork from a ThreadFork-handling stacksCalling exec from a ThreadProcess Exit and ThreadsMultiprocessor Memory Synchronization
6. Practical Considerations
Understanding Pthreads ImplementationTwo WorldsTwo Kinds of ThreadsWho’s Providing the Thread?User-space Pthreads implementationsKernel thread–based Pthreads implementationsTwo-level scheduler Pthreads implementations: the best of both worldsDebuggingDeadlockRace ConditionsEvent OrderingLess Is BetterTrace StatementsDebugger Support for ThreadsExample: Debugging the ATM ServerDebugging a deadlock caused by a missing unlockDebugging a race condition caused by a missing lockPerformanceThe Costs of Sharing Too Much—LockingThread OverheadThread context switchesSynchronization OverheadHow Do Your Threads Spend Their Time?Performance in the ATM Server ExamplePerformance depends on input workload: increasing clients and contentionPerformance depends on a good locking strategyPerformance depends on the type of work threads doKey performance issues between using threads and using processesConclusion

A. Pthreads and DCE
The Structure of a DCE ServerWhat Does the DCE Programmer Have to Do?Example: The ATM as a DCE Server
B. Pthreads Draft 4 vs. the Final Standard
Detaching a ThreadMutex VariablesCondition VariablesThread AttributesThe pthread_once FunctionKeysCancellationSchedulingSignalsThreadsafe System InterfacesError ReportingSystem Interfaces and Cancellation-SafetyProcess-Blocking CallsProcess Management
C. Pthreads Quick Reference
D. About the Authors
Index
About the Authors
Colophon
Copyright

Content preview from PThreads Programming

Appendix D. About the Authors

Brad Nichols is a freelance do-anything-computerish-for-a-buck kind of guy who works out of Milford, NH. He earned a B.S. degree in Mechanical Engineering from the University of New Hampshire in 1985 and an M.S. degree from Worcester Polytechnic Institute (WPI) in 1991. He started his computer career working on very hard hardware (fuel pumps and valves). He worked his way up through the hardware layers into software on projects involving embedded avionics systems at Textron Lycomming and United Technologies Hamilton Standard Division. Brad left these jobs to learn more about AI at WPI, but instead caught the Mach fever, and was introduced to threads programming in UNIX. While at WPI he also worked on an OSF/1 performance project for the Open Software Foundation (OSF). After attending WPI, Brad taught training seminars to software developers on the Mach kernel interfaces. He then joined Digital Equipment Corporation to work on the port of the OSF’s Distributed Computing Environment’s Distributed File System (OSFDCEDFSDU for short) to Digital UNIX. Now, Brad is once again on his own and spends most of his time teaching software engineers about technologies with much shorter acronyms—such as Pthreads.

When not working, Brad spends time at home trying to synchronize with his wife, Susan, and three little threads, Dan (who’s 7), Tim (5), and Cecelia (3). And, oh yes, there’s the lawn and dump things on weekends too.

Dick Buttlar is a consulting writer in the ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781449364724Errata Page

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

PThreads Programming

by Dick Buttlar, Jacqueline Farrell, Bradford Nichols

Appendix D. About the Authors

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.