Processes in Unix, Linux, and Windows.ppt

CS-3013 C-term 2008 Process in Unix, Linux and Windows Processes in Unix, Linux, and Windows CS-3013 Operating Systems (Slides include materials from Operating System Concepts, 7th ed., by Silbershatz, Galvin, Gagne and from Modern Operating Systems, 2nd ed., by Tanenbaum) Processes in Unix, Linux, and Windows Unix pre-empted generic term “process” to mean something very specific Linux and Windows adopted Unix definition Process in Unix-Linux-Windowscomprises an address space – usually protected and virtual – mapped into memory the code for the running program the data for the running program an execution stack and stack pointer (SP); also heap the program counter (PC) a set of processor registers – general purpose and status a set of system resources files, network connections, pipes, … privileges, (human) user association, … … Processes – Address Space Processes in the OS – Representation To users (and other processes) a process is identified by its Process ID (PID) In the OS, processes are represented by entries in a Process Table (PT) PID is index to (or pointer to) a PT entry PT entry = Process Control Block (PCB) PCB is a large data structure that contains or points to all info about the process Linux - defined in task_struct – over 70 fields see include/linux/sched.h Windows XP – defined in EPROCESS – about 60 fields Processes in the OS – PCB Typical PCB contains: execution state PC, SP processor registers – stored when process is not in running state memory management info Privileges and owner info scheduling priority resource info accounting info Process – starting and ending Processes are created … When the system boots By the actions of another process (more later) By the actions of a user By the actions of a batch manager Processes terminate … Normally – exit Voluntarily on an error Involuntarily on an error Terminated (killed) by the actions a user or a process Processes – States Process has an execution state ready: waiting to be assigned to CP