Presentation is loading. Please wait.

Presentation is loading. Please wait.

Chapter 4: Threads.

Similar presentations


Presentation on theme: "Chapter 4: Threads."— Presentation transcript:

1 Chapter 4: Threads

2 Chapter 4: Threads Overview Multithreading Models Threading Issues
Pthreads Windows XP Threads Linux Threads Java Threads

3 Single and Multithreaded Processes

4 Benefits Responsiveness Resource Sharing Economy
Utilization of MP Architectures

5 Excursion: Programming Models
UI and network programs have multiple event sources network packets, user input, media input (audio/video) Can never block: event-based --> finite-state machine only very short, non-blocking fragments asynchronous system calls start, wait for event, transition thread-based block for each logical thread of execution naturally sequential operations can’t read web page until domain name has been resolved read URL query DNS show error receive response open socket connect succeeds send request receive response display page

6 User and Kernel Threads
User threads - Thread management done by user-level threads library. Kernel threads - Threads directly supported by the kernel.

7 Kernel Threads Examples Windows XP/2000 Solaris Linux Tru64 UNIX
Mac OS X

8 Multithreading Models
Mapping user threads to kernel threads: Many-to-One One-to-One Many-to-Many

9 Many-to-One Many user-level threads mapped to single kernel thread
Examples: Solaris Green Threads GNU Portable Threads

10 Many-to-One Model

11 One-to-One Each user-level thread maps to kernel thread Examples
Windows NT/XP/2000 Linux Solaris 9 and later

12 One-to-one Model

13 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

14 Many-to-Many Model

15 Two-level Model Similar to M:M, except that it allows a user thread to be bound to kernel thread Examples IRIX HP-UX Tru64 UNIX Solaris 8 and earlier

16 Two-level Model

17 Java Threads Java threads are managed by the JVM
Java threads may be created by: Implementing the Runnable interface

18 Java Threads - Example Program

19 Java Threads - Example Program

20 Java Thread States

21 Java Threads - Producer-Consumer

22 Java Threads - Producer-Consumer

23 Java Threads - Producer-Consumer

24 Threading Issues Semantics of fork() and exec() system calls
Thread cancellation Signal handling Thread pools Thread specific data Scheduler activations

25 Semantics of fork() and exec()
Does fork() duplicate only the calling thread or all threads?

26 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

27 Deferred cancellation in Java
Thread Cancellation Deferred cancellation in Java Interrupting a thread

28 Thread Cancellation Deferred cancellation in Java
Checking interruption status

29 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 signals Signal is generated by particular event Signal is delivered to a process Signal is handled Options: Deliver the signal to the thread to which the signal applies Deliver the signal to every thread in the process Deliver the signal to certain threads in the process Assign a specific threa to receive all signals for the process

30 Unix signal handling: asynchronous
#include <signal.h> #include <stdio.h> void sigint(int sig) { printf("signal handler %d\n", sig); /* re-set the signal handler again for next time */ signal(SIGINT, sigint); } int main(int argc, char *argv[]) while (1) { sleep(5);

31 Unix signal handling: synchronous
#include <signal.h> #include <setjmp.h> #include <stdio.h> #include <unistd.h> int div; static jmp_buf env; void sigfpe(int sig) { printf("signal handler %d\n", sig); div = 2; siglongjmp(env, 1); } int main(int argc, char *argv[]) int x = 42; signal(SIGFPE, sigfpe); printf("before division\n"); div = 0; if (sigsetjmp(env,0) != 0) { printf("we tried to divide by zero: %d!\n", div); x /= div; printf("after division: %d %d\n", x, div); return 0;

32 Signal advice Very similar to interrupt handlers
Keep signal handlers short Mask signals to avoid signal-in-signal sigprocmask() Use fault signals for cleanup, not fixup SIGBUS, SIGSEGV, SIGFPE Can only use a single alarm() timer need timer manager otherwise Signals are relatively slow lots of context switches asynchronous I/O Don’t rely on restart too much Avoid longjmp()

33 Thread Pools Create 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 thread Allows the number of threads in the application(s) to be bound to the size of the pool

34 Thread Pools Java provides 3 thread pool architectures: 1. Single thread executor - pool of size Fixed thread executor - pool of fixed size Cached thread pool - pool of unbounded size

35 Thread Pools A task to be serviced in a thread pool

36 Thread Pools Creating a thread pool in Java

37 Thread Specific Data Allows 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)

38 Thread Specific Data Thread-specific data in Java.

39 Scheduler Activations
Both 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

40 Pthreads A POSIX standard (IEEE c) 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)

41 Windows XP Threads Implements the one-to-one mapping
Each thread contains A thread id Register set Separate user and kernel stacks Private data storage area The register set, stacks, and private storage area are known as the context of the threads

42 Windows XP Threads

43 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)

44 End of Chapter 4


Download ppt "Chapter 4: Threads."

Similar presentations


Ads by Google