Processes. CSE 351 Autumn Instructor: Justin Hsia

Similar documents
Processes. CSE 351 Autumn Instructor: Justin Hsia

University of Washington What is a process?

CSC 252: Computer Organization Spring 2018: Lecture 19

Processes: Introduction. CS 241 February 13, 2012

Processes. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

Processes. CSE 351 Spring Instructor: Ruth Anderson

Processes, Virtual Memory I

Q & A (1) Where were string literals stored? Virtual Address. SSE2033: System Software Experiment 2 Spring 2016 Jin-Soo Kim

Are branches/calls the only way we can get the processor to go somewhere in a program? What is a program? A processor? A process?

Announcement (1) sys.skku.edu is now available

Roadmap. Java: Assembly language: OS: Machine code: Computer system:

Exceptional Control Flow: Exceptions and Processes

Today. Exceptional Control Flow Processes. Exceptions and Processes. Control Flow. Altering the Control Flow

Exceptional Control Flow Part I September 22, 2008

Exceptional Control Flow Part I

Today. Introduction to Computer Systems /18 243, Fall th Lecture. Control Flow. Altering the Control Flow.

Carnegie Mellon. Processes. Lecture 12, May 19 th Alexandre David. Credits to Randy Bryant & Dave O Hallaron from Carnegie Mellon

Exceptional Control Flow Part I Oct. 17, 2002

Control Flow. Systemprogrammering 2007 Föreläsning 2 Exceptional Control Flow Part I. Exceptional Control Flow. Altering the Control Flow

Giving credit where credit is due

Exceptional Control Flow Part I

Exceptions, Processes and Signals

Exceptional Control Flow: Exceptions and Processes

Exceptional Control Flow Part I Oct. 28, 2009"

Processes, Exceptional

Introduction to Computer Systems , fall th Lecture, Oct. 7 th

CSE351 Inaugural Edi7on Spring

Approaches to Concurrency

Excep&onal+Control+Flow:++ Excep&ons+and+Processes+ + 15C213':'Introduc;on'to'Computer'Systems' 14 th 'Lecture,'Oct.'15,'2015'

Excep&onal Control Flow: Excep&ons and Processes

Virtual Memory I. CSE 351 Autumn Instructor: Justin Hsia

Excep onal Control Flow: Excep ons and Processes

Are branches/calls the only way we can get the processor to go somewhere in a program? What is a program? A processor? A process?

Program and OS interac0ons: Excep0ons and Processes

OS Interaction and Processes

Foundations of Computer Systems

Foundations of Computer Systems

Altering the Control Flow

Excep&onal Control Flow: Excep&ons and Processes. (Chapter 8)

Altering the Control Flow

CS 201. Processes. Gerson Robboy Portland State University

Exceptions and Processes

CS3733: Operating Systems

PROCESS PROGRAMMING INTERFACE

CS24: INTRODUCTION TO COMPUTING SYSTEMS. Spring 2018 Lecture 20

Virtual Memory I. CSE 351 Winter Instructor: Mark Wyse

CSC 1600 Unix Processes. Goals of This Lecture

!"#$%&'()*+,'(-.'*+/*'01+!"#$%&'(2+)(3+4.'#$22$2

CMPSCI 230 Computer Systems Principles. Processes

Processes & Signals. System Runs Many Processes Concurrently. State consists of memory image + register values + program counter

Shell and Signals. Computer Organization 3/17/2015. CSC252 - Spring The World of Multiprogramming or Multitasking. Unix Process Hierarchy

fork System-Level Function

Operating System Structure

Process Control. Philipp Koehn. 23 April 2018

Exceptional Control Flow Part II Nov. 2, 2009"

Operating System. Chapter 3. Process. Lynn Choi School of Electrical Engineering

Princeton University Computer Science 217: Introduction to Programming Systems. Process Management

Princeton University Computer Science 217: Introduction to Programming Systems. Process Management

Princeton University. Computer Science 217: Introduction to Programming Systems. Process Management

Multitasking. Programmer s model of multitasking. fork() spawns new process. exit() terminates own process

CSci 4061 Introduction to Operating Systems. Processes in C/Unix

Lesson 2. process id = 1000 text data i = 5 pid = 1200

Signals. Jin-Soo Kim Computer Systems Laboratory Sungkyunkwan University

Exceptions, Processes and Signals

System Programming. Process Control II

Unix Processes 1 / 31

Lecture 24: Multitasking and Signals

Week 2 Intro to the Shell with Fork, Exec, Wait. Sarah Diesburg Operating Systems CS 3430

CSCI2467: Systems Programming Concepts

CS213. Exceptional Control Flow Part II. Topics Process Hierarchy Signals

Process Management 1

Operating Systems Components. What is an Operating System? Process Management. Memory Management. Operating Systems 9/7/2018 CSC 256/456 1

Processes, Exceptional Control Flow

Programming Assignments will be.. All the PAs are continuous 3 major factors that you should consider

CS240: Programming in C

CSCB09: Software Tools and Systems Programming. Bianca Schroeder IC 460

Introduction to Processes

CPSC 341 OS & Networks. Processes. Dr. Yingwu Zhu

CS 550 Operating Systems Spring Process III

CS 475. Process = Address space + one thread of control Concurrent program = multiple threads of control

Process Management. Outline. Process vs. Program. Address Space. How do we run a program? What are steps to create a process?

Caches II. CSE 351 Autumn Instructor: Justin Hsia

Processes & Threads. (Chapter 3) CS 4410 Operating Systems. [R. Agarwal, L. Alvisi, A. Bracy, M. George, E. Sirer, R. Van Renesse]

CS 261 Fall Mike Lam, Professor. Processes

UNIX Processes. by Armin R. Mikler. 1: Introduction

The Stack & Procedures

Exceptional Control Flow Exists at All Levels of a System. Systemprogrammering 2007 Föreläsning 3 Exceptional Control Flow Part II

CS 3733 Operating Systems

ECF Exists at All Levels of a System Exceptional Control Flow Part II Oct. 22, 2002 Topics! Process Hierarchy! Shells! Signals!

Unix-Linux 2. Unix is supposed to leave room in the process table for a superuser process that could be used to kill errant processes.

CS 31: Intro to Systems Processes. Kevin Webb Swarthmore College March 31, 2016

Process Management! Goals of this Lecture!

Exceptional Control Flow Part II

Operating systems and concurrency - B03

Giving credit where credit is due

518 Lecture Notes Week 3

Processes. CS3026 Operating Systems Lecture 05

CS 261 Fall Mike Lam, Professor. Exceptional Control Flow and Processes

CSC209H Lecture 6. Dan Zingaro. February 11, 2015

Process Management 1

Transcription:

Processes CSE 351 Autumn 2017 Instructor: Justin Hsia Teaching Assistants: Lucas Wotton Michael Zhang Parker DeWilde Ryan Wong Sam Gehman Sam Wolfson Savanna Yee Vinny Palaniappan http://xkcd.com/292/

Administrivia Homework 4 due Friday (11/17) Lab 4 due after Thanksgiving (11/27) Parts of this lab are new, so don t hesitate to ask if anything is unclear or seem buggy! 2

Processes Processes and context switching Creating new processes fork(), exec*(), and wait() Zombies 3

What is a process? It s an illusion! Process 1 Memory CPU Disk Registers %rip Chrome.exe 4

What is a process? Another abstraction in our computer system Provided by the OS OS uses a data structure to represent each process Maintains the interface between the program and the underlying hardware (CPU + memory) What do processes have to do with exceptional control flow? Exceptional control flow is the mechanism the OS uses to enable multiple processes to run on the same system What is the difference between: A processor? A program? A process? 5

Processes A process is an instance of a running program One of the most profound ideas in computer science Not the same as program or processor Process provides each program with two key abstractions: Logical control flow Each program seems to have exclusive use of the CPU Provided by kernel mechanism called context switching Private address space Each program seems to have exclusive use of main memory Provided by kernel mechanism called virtual memory Memory CPU Registers 6

What is a process? It s an illusion! Computer Process 3 Process 2 Memory CPU Registers Process 1 Memory Memory CPU Registers Process 4 Memory CPU Registers CPU Registers CPU Disk /Applications/ Chrome.exe Slack.exe PowerPoint.exe 7

What is a process? It s an illusion! Computer Process 3 Process 2 Memory CPU Registers Process 1 Memory Memory CPU Registers Process 4 Memory Operating System CPU CPU Registers CPU Registers Disk /Applications/ Chrome.exe Slack.exe PowerPoint.exe 8

Multiprocessing: The Illusion Memory Memory Memory CPU CPU CPU Registers Registers Registers Computer runs many processes simultaneously Applications for one or more users Web browsers, email clients, editors, Background tasks Monitoring network & I/O devices 9

Multiprocessing: The Reality Memory Saved registers Saved registers Saved registers CPU Registers Single processor executes multiple processes concurrently Process executions interleaved, CPU runs one at a time Address spaces managed by virtual memory system (later in course) Execution context (register values, stack, ) for other processes saved in memory 10

Multiprocessing Memory Saved registers Saved registers Saved registers CPU Registers Context switch 1) Save current registers in memory 11

Multiprocessing Memory Saved registers Saved registers Saved registers CPU Registers Context switch 1) Save current registers in memory 2) Schedule next process for execution 12

Multiprocessing Memory Saved registers Saved registers Saved registers CPU Registers Context switch 1) Save current registers in memory 2) Schedule next process for execution 3) Load saved registers and switch address space 13

Multiprocessing: The (Modern) Reality Memory Saved registers Saved registers Saved registers CPU Registers CPU Registers Multicore processors Multiple CPUs ( cores ) on single chip Share main memory (and some of the caches) Each can execute a separate process Kernel schedules processes to cores Still constantly swapping processes 14

Concurrent Processes Assume only one CPU Each process is a logical control flow Two processes run concurrently (are concurrent) if their instruction executions (flows) overlap in time Otherwise, they are sequential Example: (running on single core) Concurrent: A & B, A & C Sequential: B & C Process A Process B Process C time 15

User s View of Concurrency Assume only one CPU Control flows for concurrent processes are physically disjoint in time CPU only executes instructions for one process at a time However, the user can think of concurrent processes as executing at the same time, in parallel Process A Process B Process C Process A Process B Process C time User View 16

Context Switching Assume only one CPU Processes are managed by a shared chunk of OS code called the kernel The kernel is not a separate process, but rather runs as part of a user process In x86 64 Linux: Same address in each process refers to same shared memory location 17

Context Switching Assume only one CPU Processes are managed by a shared chunk of OS code called the kernel The kernel is not a separate process, but rather runs as part of a user process Context switch passes control flow from one process to another and is performed using kernel code Process A Process B time user code kernel code user code kernel code user code context switch context switch 18

Processes Processes and context switching Creating new processes fork(), exec*(), and wait() Zombies 19

Creating New Processes & Programs Process 1 Process 2 Memory fork() Memory CPU Registers CPU Registers exec*() Chrome.exe 20

Creating New Processes & Programs fork exec model (Linux): fork() creates a copy of the current process exec*() replaces the current process code and address space with the code for a different program Family: execv, execl, execve, execle, execvp, execlp fork() and execve() are system calls Other system calls for process management: getpid() exit() wait(), waitpid() 21

fork: Creating New Processes pid_t fork(void) Creates a new child process that is identical to the calling parent process, including all state (memory, registers, etc.) Returns 0 to the child process Returns child s process ID (PID) to the parent process Child is almost identical to parent: Child gets an identical (but separate) copy of the parent s virtual address space Child has a different PID than the parent pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); fork is unique (and often confusing) because it is called once but returns twice 22

Understanding fork Process X (parent) pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); Process Y (child) pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); 23

Understanding fork Process X (parent) pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); Process Y (child) pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid = Y pid = 0 24

Understanding fork Process X (parent) pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); Process Y (child) pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid_t pid = fork(); if (pid == 0) { printf("hello from child\n"); else { printf("hello from parent\n"); pid = Y pid = 0 hello from parent hello from child Which one appears first? 25

Fork Example Both processes continue/start execution after fork Child starts at instruction after the call to fork (storing into pid) Can t predict execution order of parent and child Both processes start with x=1 void fork1() { int x = 1; pid_t pid = fork(); if (pid == 0) printf("child has x = %d\n", ++x); else printf("parent has x = %d\n", --x); printf(" from process %d with x = %d\n", getpid(), x); Subsequent changes to x are independent Shared open files: stdout is the same in both parent and child 26

Modeling fork with Process Graphs A process graph is a useful tool for capturing the partial ordering of statements in a concurrent program Each vertex is the execution of a statement a b means a happens before b Edges can be labeled with current value of variables printf vertices can be labeled with output Each graph begins with a vertex with no inedges Any topological sort of the graph corresponds to a feasible total ordering Total ordering of vertices where all edges point from left to right 27

Fork Example: Possible Output void fork1() { int x = 1; pid_t pid = fork(); if (pid == 0) printf("child has x = %d\n", ++x); else printf("parent has x = %d\n", --x); printf(" from process %d with x = %d\n", getpid(), x); x=2 Child ++x printf printf x=0 Parent x=1 fork --x printf printf 28

Peer Instruction Question Are the following sequences of outputs possible? Vote at http://pollev.com/justinh void nestedfork() { printf("l0\n"); if (fork() == 0) { printf("l1\n"); if (fork() == 0) { printf("l2\n"); printf("\n"); Seq 1: L0 L1 L2 Seq 2: L0 L1 L2 A. No No B. No Yes C. Yes No D. Yes Yes E. We re lost 29

Fork Exec Note: the return values of fork and exec* should be checked for errors fork exec model: fork() creates a copy of the current process exec*() replaces the current process code and address space with the code for a different program Whole family of exec calls see exec(3) and execve(2) // Example arguments: path="/usr/bin/ls", // argv[0]="/usr/bin/ls", argv[1]="-ahl", argv[2]=null void fork_exec(char *path, char *argv[]) { pid_t pid = fork(); if (pid!= 0) { printf("parent: created a child %d\n", pid); else { printf("child: about to exec a new program\n"); execv(path, argv); printf("this line printed by parent only!\n"); 30

Exec ing a new program : /usr/bin/bash fork() Very high level diagram of what happens when you run the command ls in a Linux shell: This is the loading part of CALL! parent child child exec*() : /usr/bin/bash : /usr/bin/bash : /usr/bin/ls 31

This is extra execve Example (non testable) material Execute /usr/bin/ls l lab4 in child process using current environment: (argc == 3) myargv environ myargv[argc] = NULL myargv[2] myargv[1] myargv[0] envp[n] = NULL envp[n-1]... envp[0] lab4 -l /usr/bin/ls PWD=/homes/iws/jhsia USER=jhsia if ((pid = fork()) == 0) { /* Child runs program */ if (execve(myargv[0], myargv, environ) < 0) { printf("%s: Command not found.\n", myargv[0]); exit(1); Run the printenv command in a Linux shell to see your own environment variables 32

Structure of the when a new program starts argv (in %rsi) Null terminated environment variable strings Null terminated command line arg strings envp[n] == NULL envp[n-1]... envp[0] argv[argc] = NULL argv[argc-1]... argv[0] Bottom of stack environ (global var) envp (in %rdx) This is extra (non testable) material argc (in %rdi) frame for libc_start_main Future stack frame for main Top of stack 33

exit: Ending a process void exit(int status) Exits a process Status code: 0 is used for a normal exit, nonzero for abnormal exit 34

Processes Processes and context switching Creating new processes fork(), exec*(), and wait() Zombies 35

Zombies When a process terminates, it still consumes system resources Various tables maintained by OS Called a zombie (a living corpse, half alive and half dead) Reaping is performed by parent on terminated child Parent is given exit status information and kernel then deletes zombie child process What if parent doesn t reap? If any parent terminates without reaping a child, then the orphaned child will be reaped by init process (pid == 1) Note: on more recent Linux systems, init has been renamed systemd In long running processes (e.g. shells, servers) we need explicit reaping 36

wait: Synchronizing with Children int wait(int *child_status) Suspends current process (i.e. the parent) until one of its children terminates Return value is the PID of the child process that terminated On successful return, the child process is reaped If child_status!= NULL, then the *child_status value indicates why the child process terminated Special macros for interpreting this status see man wait(2) Note: If parent process has multiple children, wait will return when any of the children terminates waitpid can be used to wait on a specific child process 37

wait: Synchronizing with Children void fork_wait() { int child_status; if (fork() == 0) { printf("hc: hello from child\n"); exit(0); else { printf("hp: hello from parent\n"); wait(&child_status); printf("ct: child has terminated\n"); printf("\n"); fork HC printf HP exit CT printf wait printf forks.c Feasible output: HC HP CT Infeasible output: HP CT HC 38

Example: Zombie linux>./forks 7 & [1] 6639 Running Parent, PID = 6639 Terminating Child, PID = 6640 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6639 ttyp9 00:00:03 forks 6640 ttyp9 00:00:00 forks <defunct> 6641 ttyp9 00:00:00 ps linux> kill 6639 [1] Terminated linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6642 ttyp9 00:00:00 ps void fork7() { if (fork() == 0) { /* Child */ printf("terminating Child, PID = %d\n", getpid()); exit(0); else { printf("running Parent, PID = %d\n", getpid()); while (1); /* Infinite loop */ forks.c ps shows child process as defunct Killing parent allows child to be reaped by init 39

Example: Non terminating Child void fork8() { if (fork() == 0) { /* Child */ printf("running Child, PID = %d\n", getpid()); while (1); /* Infinite loop */ else { printf("terminating Parent, PID = %d\n", getpid()); exit(0); forks.c linux>./forks 8 Terminating Parent, PID = 6675 Running Child, PID = 6676 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6676 ttyp9 00:00:06 forks 6677 ttyp9 00:00:00 ps linux> kill 6676 linux> ps PID TTY TIME CMD 6585 ttyp9 00:00:00 tcsh 6678 ttyp9 00:00:00 ps Child process still active even though parent has terminated Must kill explicitly, or else will keep running indefinitely 40

Process Management Summary fork makes two copies of the same process (parent & child) Returns different values to the two processes exec* replaces current process from file (new program) Two process program: First fork() if (pid == 0) { /* child code */ else { /* parent code */ Two different programs: First fork() if (pid == 0) { execv( ) else { /* parent code */ wait or waitpid used to synchronize parent/child execution and to reap child process 41

Summary Processes At any given time, system has multiple active processes On a one CPU system, only one can execute at a time, but each process appears to have total control of the processor OS periodically context switches between active processes Implemented using exceptional control flow Process management fork: one call, two returns execve: one call, usually no return wait or waitpid: synchronization exit: one call, no return 42

Detailed examples: Consecutive forks wait() example waitpid() example 43

Example: Two consecutive forks void fork2() { printf("l0\n"); fork(); printf("l1\n"); fork(); printf("\n"); L1 printf fork L0 L1 printf fork printf fork printf printf printf printf Feasible output: L0 L1 L1 Infeasible output: L0 L1 L1 44

Example: Three consecutive forks Both parent and child can continue forking void fork3() { printf("l0\n"); fork(); printf("l1\n"); fork(); printf("l2\n"); fork(); printf("\n"); L0 L1 L2 L1 L2 L2 L2 45

wait() Example If multiple children completed, will take in arbitrary order Can use macros WIFEXITED and WEXITSTATUS to get information about exit status void fork10() { pid_t pid[n]; int i; int child_status; for (i = 0; i < N; i++) if ((pid[i] = fork()) == 0) exit(100+i); /* Child */ for (i = 0; i < N; i++) { pid_t wpid = wait(&child_status); if (WIFEXITED(child_status)) printf("child %d terminated with exit status %d\n", wpid, WEXITSTATUS(child_status)); else printf("child %d terminated abnormally\n", wpid); 46

waitpid(): Waiting for a Specific Process pid_t waitpid(pid_t pid,int &status,int options) suspends current process until specific process terminates various options (that we won t talk about) void fork11() { pid_t pid[n]; int i; int child_status; for (i = 0; i < N; i++) if ((pid[i] = fork()) == 0) exit(100+i); /* Child */ for (i = 0; i < N; i++) { pid_t wpid = waitpid(pid[i], &child_status, 0); if (WIFEXITED(child_status)) printf("child %d terminated with exit status %d\n", wpid, WEXITSTATUS(child_status)); else printf("child %d terminated abnormally\n", wpid); 47