Linux编程线程.pptVIP

Topics Threads Pthread Pthread Mutex Pthread Condition variables Pthread Main API Threads Overview Multithreading Models Threading Issues Pthreads Windows XP Threads Linux Threads Java Threads Single vs. Multithreaded Processes use threads or processes? Why use threads instead of processes? Faster context switch Easier to share data Uses less memory and resources Thread creation faster than process creation Less things to set-up Why use processes instead of threads? Different code Running on different machines Different owners Little communication Sharing memory can lead to obscure bugs User-level threads Threads can be provided at the user or kernel level User level: kernel knows nothing about threads Implemented in a library by somebody without touching the kernel User library handles Thread creation Thread deletion Thread scheduling Benefits: Faster creation and scheduling Drawbacks: One thread blocking during I/O blocks all threads in process (even ready-to-run threads) User-level threads (cont’d) Three primary thread libraries: POSIX Pthreads Win32 threads Java threads Kernel-level threads Kernel knows about threads Kernel handles thread creation, deletion, scheduling Benefits: Kernel can schedule another thread if current one does blocking I/O Kernel can schedule multiple threads on different CPUs on SMP multiprocessor Drawbacks: Slower to schedule, create, delete than user-level Most modern OSes support kernel-level threads Windows XP/2000 Solaris Linux Tru64 UNIX Mac OS X Multithreading Models How to map kernel-level threads to user-level threads? Many-to-One One-to-One Many-to-Many Many-to-One Model Many-to-One Many user-level threads mapped to single kernel thread Examples: Solaris Green Threads GNU Portable Threads Any disadvantages? All block when one blocks All run on 1 CPU One-to-one Model One-to-One Each user-level thread maps to a kernel thread Examples: Windows NT/XP/2000 Linux Solaris 9 and later Any disadvantages? Overhead for creati