1. Lecture 20 Threads Richard Gesick

2. Threads Makes use of multiple processors/cores if available Share memory within the program (as opposed to processes which are separate) Must coordinate access to shared memory 14-2

3. THREADS IN THE OS Operating systems use processes to separate the different applications that they are executing. Threads are the basic unit to which an operating system allocates processor time, and more than one thread can be executing code inside that process. Each thread maintains exception handlers, a scheduling priority, and a set of structures the system uses to save the thread context until it is scheduled. The thread context includes all the information the thread needs to seamlessly resume execution, including the thread's set of CPU registers and stack, in the address space of the thread's host process. 1-3

4. Threads in the OS An operating system that supports preemptive multitasking creates the effect of simultaneous execution of multiple threads from multiple processes. It does this by dividing the available processor time among the threads that need it, allocating a processor time slice to each thread one after another. The currently executing thread is suspended when its time slice elapses, and another thread resumes running. When the system switches from one thread to another, it saves the thread context of the preempted thread and reloads the saved thread context of the next thread in the thread queue. The length of the time slice depends on the operating system and the processor. Because each time slice is small, multiple threads appear to be executing at the same time, even if there is only one processor. This is actually the case on multiprocessor systems, where the executable threads are distributed among the available processors. 1-4

5. Threads Easy to make a separate worker (thread) within a larger program: Define worker function/method Create thread and tell it what method to run when it's started Run/start thread 14-5

6. Threads There is a problem with this, though, in that the method that the thread runs does not take in any parameters. To solve this, use a class: Define a class that takes in any needed parameters in its constructor Store the values into object-level attributes The last thing the constructor does is create a thread and run it (invoking an internal method of the class) This worker thread then has access to all the attributes 14-6

7. Example class Program { static void Main(string[] args) { // Bring to life 10 threaded workers and let the run! for (int i = 0; i < 10; i++) { ThreadedWorker tr = new ThreadedWorker(i); } 14-7

8. The worker public class ThreadedWorker { // A unique ID to identify this thread (for printing) int ID; // The thread Thread t; // Constructor public ThreadedWorker(int ID) { this.ID = ID; // Bring the thread to life t = new Thread(new ThreadStart(doWork)); t.Start(); } 14-8

9. do work // The method that we're going to run for the thread void doWork() { for (int i = 0; i < 10; i++) { Console.WriteLine("Thread " + ID + " is running"); } Console.WriteLine("Thread "+ID+" is finished"); } 1-9

10. Simple "Cornflower Blue" XNA Game 14-10

11. After adding worker threads to the game 14-11