v1stanford.edu-Processes_and_Threads

v1stanford.edu-Processes_and_Threads - Processes and...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
http://w w w .stanford.edu/~ouster/cgi-bin/cs140-w inter12/lecture.php?topic=process January 11, 2012 Processes and Threads Processes and Threads Lecture Notes for CS 140 Winter 2012 John Ousterhout Readings for this topic from Operating System Concepts : Sections 1.1-1.6, Section 3.1, and Section 3.3. Processes Process (slightly oversimplified): "An execution stream in the context of a particular process state." Execution stream: a sequence of instructions (only one thing happens at a time). Process state: everything that can affect, or be affected by, the process: code, registers, data, call stack, open files, network connections, etc. Is a process the same as a program? Uniprogramming system : only supports a single process at a time. Simplifies some parts of OS, but many other things are hard to do. Some early personal computer operating systems used uniprogramming (e.g. MS- DOS), but these systems are almost unheard of today. This is not the same as "uniprocessing": that refers to a system with only one processor. Virtually all modern operating systems are multiprogramming systems : multiple processes can exist simultaneously and share the machine. Threads
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 2
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 04/02/2012 for the course CS 140 taught by Professor Rosenblum during the Winter '08 term at Stanford.

Page1 / 3

v1stanford.edu-Processes_and_Threads - Processes and...

This preview shows document pages 1 - 2. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online