1. Silberschatz, Galvin and Gagne  2002 5.1 Operating System Concepts Chapter 5: Threads Overview Multithreading Models Threading Issues Pthreads Solaris 2 Threads Windows 2000 Threads Linux Threads Java Threads

2. Silberschatz, Galvin and Gagne  2002 5.2 Operating System Concepts Single and Multithreaded Processes

3. Silberschatz, Galvin and Gagne  2002 5.3 Operating System Concepts Benefits Responsiveness Resource Sharing Economy Utilization of MP Architectures

4. Silberschatz, Galvin and Gagne  2002 5.4 Operating System Concepts User Threads Thread management done by user-level threads library Examples - POSIX Pthreads - Mach C-threads - Solaris threads

5. Silberschatz, Galvin and Gagne  2002 5.5 Operating System Concepts Kernel Threads Supported by the Kernel Examples - Windows 95/98/NT/2000 - Solaris - Tru64 UNIX - BeOS - Linux

6. Silberschatz, Galvin and Gagne  2002 5.6 Operating System Concepts Multithreading Models Many-to-One One-to-One Many-to-Many

7. Silberschatz, Galvin and Gagne  2002 5.7 Operating System Concepts Many-to-One Many user-level threads mapped to single kernel thread. Used on systems that do not support kernel threads.

8. Silberschatz, Galvin and Gagne  2002 5.8 Operating System Concepts Many-to-One Model

9. Silberschatz, Galvin and Gagne  2002 5.9 Operating System Concepts One-to-One Each user-level thread maps to kernel thread. Examples - Windows 95/98/NT/2000 - OS/2

10. Silberschatz, Galvin and Gagne  2002 5.10 Operating System Concepts One-to-one Model

11. Silberschatz, Galvin and Gagne  2002 5.11 Operating System Concepts 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 2 Windows NT/2000 with the ThreadFiber package

12. Silberschatz, Galvin and Gagne  2002 5.12 Operating System Concepts Many-to-Many Model

13. Silberschatz, Galvin and Gagne  2002 5.13 Operating System Concepts Threading Issues Semantics of fork() and exec() system calls. Thread cancellation. Signal handling Thread pools Thread specific data

14. Silberschatz, Galvin and Gagne  2002 5.14 Operating System Concepts The fork and exec system calls Two versions of fork()  Duplicates all threads: not necessary if exec is called immediately  Duplicates only the thread that invoked the fork system call

15. Silberschatz, Galvin and Gagne  2002 5.15 Operating System Concepts Thread cancellation Task of terminating a thread before is has completed Two different scenarios:  Asynchronous cancellation  Deferred cancellation Difficulty occurs when:  Resources have been allocated to a cancelled thread  While the cancelled thread is updating shared data Problems can be alleviated with deferred cancellation at cancellation point

16. Silberschatz, Galvin and Gagne  2002 5.16 Operating System Concepts Signal Handling A signal is used to notify a process that a particular event has occurred. e.g. divide by zero, illegal memory access A signal can be received:  Synchronously: delivered to the process causing the signal  Asynchronously: generated by an external event Signal pattern:  A signal is generated by the occurrence of a particular event  A generated signal is delivered to a process  Once delivered, the signal must be handled Handler:  Default signal handler  User-defined handler

17. Silberschatz, Galvin and Gagne  2002 5.17 Operating System Concepts Signal Handling Where should a signal be delivered: (depend on signal type)  Thread to which the signal applies  Every thread in the process  Certain thread in the process  A specific thread assigned (APC)

18. Silberschatz, Galvin and Gagne  2002 5.18 Operating System Concepts Thread Pools Creating a separate thread is superior than creating a separate process when a server receiving a request:  Less time for creating thread  However, unlimited threads could exhaust system resources Thread Pools: to create a number of threads at process startup and place them into a pool If the pool contains no available thread, the server waits until one becomes free

19. Silberschatz, Galvin and Gagne  2002 5.19 Operating System Concepts Thread-Specific Data Each thread needs its own copy of certain data in some circumstances

20. Silberschatz, Galvin and Gagne  2002 5.20 Operating System Concepts Pthreads 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.

21. Silberschatz, Galvin and Gagne  2002 5.21 Operating System Concepts Solaris 2 Threads

22. Silberschatz, Galvin and Gagne  2002 5.22 Operating System Concepts Solaris Process

23. Silberschatz, Galvin and Gagne  2002 5.23 Operating System Concepts Windows 2000 Threads Implements the one-to-one mapping. Each thread contains - a thread id - register set - separate user and kernel stacks - private data storage area

24. Silberschatz, Galvin and Gagne  2002 5.24 Operating System Concepts 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)

25. Silberschatz, Galvin and Gagne  2002 5.25 Operating System Concepts Java Threads Java threads may be created by:  Extending Thread class  Implementing the Runnable interface Java threads are managed by the JVM.

26. Silberschatz, Galvin and Gagne  2002 5.26 Operating System Concepts Java Thread States