chapter 4: threads - yale universitycodex.cs.yale.edu/avi/os-book/ose1/slide-dir/pdf-dir/ch4.pdf ·...
TRANSCRIPT
Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Chapter 4: Threads
4.2 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Chapter 4: ThreadsOverviewMultithreading ModelsThread LibrariesThreading IssuesOperating System ExamplesWindows XP ThreadsLinux Threads
4.3 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
ObjectivesTo introduce the notion of a thread — a fundamental unit of CPU utilization that forms the basis of multithreaded computer systems
To discuss the APIs for the Pthreads, Win32, and Java thread libraries
To examine issues related to multithreaded programming
4.4 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
MotivationThreads run within applicationMultiple tasks with the application can be implemented by separate threads
Update displayFetch dataSpell checkingAnswer a network request
Process creation is heavy-weight while thread creation is light-weightCan simplify code, increase efficiencyKernels are generally multithreaded
4.5 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Single and Multithreaded Processes
4.6 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Benefits
Responsiveness
Resource Sharing
Economy
Scalability
4.7 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Multicore ProgrammingMulticore systems putting pressure on programmers, challenges include:
Dividing activitiesBalanceData splittingData dependencyTesting and debugging
4.8 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Multithreaded Server Architecture
4.9 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Concurrent Execution on a Single-core System
4.10 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Parallel Execution on a Multicore System
4.11 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
User ThreadsThread management done by user-level threads library
Three primary thread libraries:POSIX PthreadsWin32 threadsJava threads
4.12 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Kernel ThreadsSupported by the Kernel
ExamplesWindows XP/2000SolarisLinuxTru64 UNIXMac OS X
4.13 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Multithreading ModelsMany-to-One
One-to-One
Many-to-Many
4.14 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Many-to-OneMany user-level threads mapped to single kernel thread
Examples:Solaris Green ThreadsGNU Portable Threads
4.15 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Many-to-One Model
4.16 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
One-to-OneEach user-level thread maps to kernel thread
ExamplesWindows NT/XP/2000LinuxSolaris 9 and later
4.17 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
One-to-one Model
4.18 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Many-to-Many Model
Allows many user level threads to be mapped to many kernel threads
Allows the operating system to create a sufficient number of kernel threads
Solaris prior to version 9
Windows NT/2000 with the ThreadFiber package
4.19 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Many-to-Many Model
4.20 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Two-level Model
Similar to M:M, except that it allows a user thread to be bound to kernel thread
ExamplesIRIXHP-UXTru64 UNIXSolaris 8 and earlier
4.21 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Two-level Model
4.22 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Thread LibrariesThread library provides programmer with API for creating and managing threads
Two primary ways of implementingLibrary entirely in user spaceKernel-level library supported by the OS
4.23 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
PthreadsMay be provided either as user-level or kernel-level
A POSIX standard (IEEE 1003.1c) API for thread creation and synchronization
API specifies behavior of the thread library, implementation is up to development of the library
Common in UNIX operating systems (Solaris, Linux, Mac OS X)
4.24 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Pthreads Example
4.25 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Pthreads Example (Cont.)
4.26 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Win32 API Multithreaded C Program
4.27 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Win32 API Multithreaded C Program (Cont.)
4.28 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Java ThreadsJava threads are managed by the JVM
Typically implemented using the threads model provided by underlying OS
Java threads may be created by:
Extending Thread classImplementing the Runnable interface
4.29 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Java Multithreaded Program
4.30 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Java Multithreaded Program (Cont.)
4.31 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Threading Issues
Semantics of fork() and exec() system calls
Thread cancellation of target threadAsynchronous or deferred
Signal handlingSynchronous and asynchronous
4.32 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Threading Issues (Cont.)
Thread poolsThread-specific data
Create Facility needed for data private to threadScheduler activations
4.33 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Semantics of fork() and exec()Does fork() duplicate only the calling thread or all threads?
4.34 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Thread Cancellation
Terminating a thread before it has finished
Two general approaches:Asynchronous cancellation terminates the target thread immediately.Deferred cancellation allows the target thread to periodically check if it should be cancelled.
4.35 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Signal Handling
Signals are used in UNIX systems to notify a process that a particular event has occurred.
A signal handler is used to process signals1. Signal is generated by particular event2. Signal is delivered to a process3. Signal is handled
Options:Deliver the signal to the thread to which the signal appliesDeliver the signal to every thread in the processDeliver the signal to certain threads in the processAssign a specific thread to receive all signals for the process
4.36 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Thread PoolsCreate a number of threads in a pool where they await work
Advantages:Usually slightly faster to service a request with an existing thread than create a new threadAllows the number of threads in the application(s) to be bound to the size of the pool
4.37 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Thread Specific DataAllows each thread to have its own copy of data
Useful when you do not have control over the thread creation process (i.e., when using a thread pool)
4.38 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Scheduler ActivationsBoth M:M and Two-level models require communication to maintain the appropriate number of kernel threads allocated to the application
Scheduler activations provide upcalls - a communication mechanism from the kernel to the thread library
This communication allows an application to maintain the correct number kernel threads
4.39 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Lightweight Processes
4.40 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Operating System ExamplesWindows XP Threads
Linux Thread
4.41 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Windows XP Threads Data Structures
4.42 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Windows XP Threads
Implements the one-to-one mapping, kernel-level
Each thread containsA thread idRegister setSeparate user and kernel stacksPrivate data storage area
The register set, stacks, and private storage area are known as the context of the threads
The primary data structures of a thread include:ETHREAD (executive thread block)KTHREAD (kernel thread block)TEB (thread environment block)
4.43 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Linux Threads
Linux refers to them as tasks rather than threads
Thread creation is done through clone() system call
clone() allows a child task to share the address space of the parent task (process)
struct task_struct points to process data structures (shared or unique)
4.44 Silberschatz, Galvin and Gagne ©2011Operating System Concepts Essentials – 8th Edition
Linux Threadsfork() and clone() system calls
Doesn’t distinguish between process and threadUses term task rather than thread
clone() takes options to determine sharing on process createstruct task_struct points to process data structures (shared or unique)