计算机操作系统-ch2a精要.ppt

* The Thread Model (1) (a) Three processes each with one thread (b) One process with three threads * The Thread Model (2) Items shared by all threads in a process Items private to each thread * The Thread Model (3) Each thread has its own stack * Thread Usage Why do you use threads? Responsiveness: Multiple activities can be done at same time. They can speed up the application. Resource Sharing: Threads share the memory and the resources of the process to which they belong. Economy: They are easy to create and destroy. Utilization of MP (multiprocessor) Architectures: They are useful on multiple CPU systems. Example - Word Processor, Spreadsheet One thread interacts with the user. One formats the document (spreadsheet). One writes the file to disk periodically. Why not three processes? * Thread Usage (1) A word processor with three threads * Thread Usage(2) Example – Web server One thread, the dispatcher, distributes the requests to a worker thread. A worker thread handles the requests. * Thread Usage (2) A multithreaded Web server * Thread Usage (2) Rough outline of code for previous slide (a) Dispatcher thread (b) Worker thread * POSIX Threads Figure 2-14. Some of the Pthreads function calls. * POSIX Threads Figure 2-15. An example program using threads. * Implementation of Threads Three mechanism Implementing threads in user space Implementing threads in kernel space Hybrid Implementations * User Threads(ULT) The threads package entirely in user space, kernel doesn’t know thread Threads management done by user-level threads library Thread switch don’t need kernel privilege, user-level threads are fast to create and manage. Problem: If the kernel is single-threaded, then any user-level thread performing a blocking system call will cause the entire process to block. Examples of threads library - POSIX Pthreads - Mach C-threads - Solaris UI-threads * Implementing Threads in User Space A user-level threads package * Kernel Threads(KLT) Supported by the Kernel