Processes. CSE 2431: Introduction to Operating Systems Reading: Chap. 3, [OSC]

Similar documents
Processes. Electrical and Computer Engineering Stephen Kim ECE/IUPUI RTOS & Apps 1

Processes. Operating System Concepts with Java. 4.1 Sana a University, Dr aimen

Chapter 3: Processes. Chapter 3: Processes. Process in Memory. Process Concept. Process State. Diagram of Process State

Process Concept. Chapter 4: Processes. Diagram of Process State. Process State. Process Control Block (PCB) Process Control Block (PCB)

Chapter 4: Processes

Part Two - Process Management. Chapter 3: Processes

Chapter 4: Processes. Process Concept

Chapter 4: Processes. Process Concept

Chapter 4: Processes

Diagram of Process State Process Control Block (PCB)

Chapter 5: Processes & Process Concept. Objectives. Process Concept Process Scheduling Operations on Processes. Communication in Client-Server Systems

Chapter 3: Processes. Operating System Concepts 8 th Edition,

The Big Picture So Far. Chapter 4: Processes

Processes and More. CSCI 315 Operating Systems Design Department of Computer Science

The Big Picture So Far. Chapter 4: Processes

Chapter 3: Processes. Operating System Concepts Essentials 8 th Edition

Chapter 4: Processes. Process Concept. Process State

Chapter 3: Processes. Operating System Concepts 8 th Edition,

Chapter 3: Processes. Operating System Concepts 8 th Edition,

Chapter 4: Processes

Chapter 3: Processes

Lecture 2 Process Management

Module 4: Processes. Process Concept Process Scheduling Operation on Processes Cooperating Processes Interprocess Communication

Module 4: Processes. Process Concept Process Scheduling Operation on Processes Cooperating Processes Interprocess Communication

COP 4610: Introduction to Operating Systems (Spring 2014) Chapter 3: Process. Zhi Wang Florida State University

Chapter 3: Process Concept

Part V. Process Management. Sadeghi, Cubaleska RUB Course Operating System Security Memory Management and Protection

CHAPTER 3 - PROCESS CONCEPT

Chapter 3: Processes. Operating System Concepts 8th Edition,

Chapter 3: Process Concept

Chapter 3: Process Concept

Chapter 3: Processes. Operating System Concepts Essentials 2 nd Edition

Chapter 3: Processes. Operating System Concepts 8th Edition

OPERATING SYSTEMS. UNIT II Sections A, B & D. An operating system executes a variety of programs:

COP 4610: Introduction to Operating Systems (Spring 2016) Chapter 3: Process. Zhi Wang Florida State University

Chapter 3: Process Concept

Chapter 3: Processes. Operating System Concepts 9 th Edition

Chapter 3 Processes. Process Concept. Process Concept. Process Concept (Cont.) Process Concept (Cont.) Process Concept (Cont.)

Roadmap. Tevfik Ko!ar. CSC Operating Systems Fall Lecture - III Processes. Louisiana State University. Processes. September 1 st, 2009

Process Concept Process Scheduling Operations On Process Inter-Process Communication Communication in Client-Server Systems

Chapter 3: Process Concept

Chapter 3: Process-Concept. Operating System Concepts 8 th Edition,

Chapter 3: Processes

! The Process Control Block (PCB) " is included in the context,

Chapter 3: Processes. Operating System Concepts 8th Edition, modified by Stewart Weiss

Process. Program Vs. process. During execution, the process may be in one of the following states

Chapter 3: Processes. Operating System Concepts 9 th Edition

Process a program in execution; process execution must progress in sequential fashion. Operating Systems

What Is A Process? Process States. Process Concept. Process Control Block (PCB) Process State Transition Diagram 9/6/2013. Process Fundamentals

Process. Operating Systems (Fall/Winter 2018) Yajin Zhou ( Zhejiang University

Course: Operating Systems Instructor: M Umair. M Umair

Processes and Threads

Prepared by Prof. Hui Jiang Process. Prof. Hui Jiang Dept of Electrical Engineering and Computer Science, York University

Process. Prepared by Prof. Hui Jiang Dept. of EECS, York Univ. 1. Process in Memory (I) PROCESS. Process. How OS manages CPU usage? No.

Processes. Process Concept

Notice: This set of slides is based on the notes by Professor Perrone of Bucknell and the textbook authors Silberschatz, Galvin, and Gagne

CSI Module 2: Processes

Process Concept. Minsoo Ryu. Real-Time Computing and Communications Lab. Hanyang University.

CS307 Operating Systems Processes

Processes. Process Concept. The Process. The Process (Cont.) Process Control Block (PCB) Process State

Operating Systems. Lecture 06. System Calls (Exec, Open, Read, Write) Inter-process Communication in Unix/Linux (PIPE), Use of PIPE on command line

Outline. Interprocess Communication. Interprocess Communication. Communication Models: Message Passing and shared Memory.

PROCESS MANAGEMENT. Operating Systems 2015 Spring by Euiseong Seo

Chapter 3: Processes

Chapter 3: Processes

Process Concept Process in Memory Process State new running waiting ready terminated Diagram of Process State

CS 471 Operating Systems. Yue Cheng. George Mason University Fall 2017

ICS Principles of Operating Systems

CS Lecture 2! Processes! George Mason University! Fall 2010!

CS370 Operating Systems

Outlook. Process Concept Process Scheduling Operations on Processes. IPC Examples

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

Lecture 5: Process Description and Control Multithreading Basics in Interprocess communication Introduction to multiprocessors

CSC 539: Operating Systems Structure and Design. Spring 2006

2. PROCESS. Operating System Concepts with Java 8th Edition Silberschatz, Galvin and Gagn

Killing Zombies, Working, Sleeping, and Spawning Children

CS420: Operating Systems. Interprocess Communication

CHAPTER 2: PROCESS MANAGEMENT

Exercise (could be a quiz) Solution. Concurrent Programming. Roadmap. Tevfik Koşar. CSE 421/521 - Operating Systems Fall Lecture - IV Threads

Operating System Concepts Ch. 3: Processes

Operating Systems. Figure: Process States. 1 P a g e

Roadmap. Tevfik Ko!ar. CSC Operating Systems Spring Lecture - III Processes. Louisiana State University. Virtual Machines Processes

Operating System Design

Dept. Of Computer Science, Colorado State University

Page 1. Analogy: Problems: Operating Systems Lecture 7. Operating Systems Lecture 7

Fall 2015 COMP Operating Systems. Lab #3

CSCE 313 Introduction to Computer Systems. Instructor: Dezhen Song

Frequently asked questions from the previous class survey

CSCE 313: Intro to Computer Systems

Prepared by Prof. Hui Jiang (COSC3221) 2/9/2007

Processes. Operating System Concepts 8 th Edition

Processes. CS 416: Operating Systems Design, Spring 2011 Department of Computer Science Rutgers University

Process Concepts 8/21/2014. CS341: Operating System. Scheduling: Theoretical Analysis

Processes. Process Scheduling, Process Synchronization, and Deadlock will be discussed further in Chapters 5, 6, and 7, respectively.

Processes COMPSCI 386

CS510 Operating System Foundations. Jonathan Walpole

ENGR 3950U / CSCI 3020U Midterm Exam SOLUTIONS, Fall 2012 SOLUTIONS

Processes. CS3026 Operating Systems Lecture 05

Operating System Structure

PROCESSES. Jo, Heeseung

Transcription:

Processes CSE 2431: Introduction to Operating Systems Reading: Chap. 3, [OSC] 1

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 2

Users, Programs, Processes Users have accounts on the system Users launch programs Many users may launch same program One user may launch many instances of the same program Processes: an executing program Question: Real life analogy? 3

Real Life Analogy? One example: Recipes Programs Step 1: xxx Step 2: xxx Step 3: xxx Step 4: xxx Making dishes Processes Action Others? (Group discussion) 4

Windows Task Manager Source: https://www.windowscentral.com/how-identify-and-terminatehigh-resource-processes-using-task-manager-windows-10 5

Unix Processes: ps 6

So What Is A Process? It s one executing instance of a program It s separated from other instances It can start ( launch ) other processes It can be launched by other processes 7

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 8

The Process Model Multiprogramming of four programs Conceptual model of 4 independent, sequential processes Only one program active at any instant 9

Process Control Block (PCB): Why? PCB contains information associated with a given process: Process state Process identification (Pid) Program counter CPU registers CPU scheduling information Memory-management information Accounting information I/O status information Pid of parent process 10

Process Descriptor in Linux (I) 11

Process Descriptor in Linux (II) In <linux/sched.h>: https://github.com/torvalds/linux/blob/master/kernel/sched/sched.h In <asm/thread_info.h>: https://github.com/torvalds/linux/blob/master/arch/x86/include/asm/thread_info.h 12

Process States As a process executes, it changes its state: New: The process is being created. Running: Instructions are being executed. Waiting (blocked): The process is waiting for some event to occur. Ready: The process is waiting to be assigned to a CPU. Terminated: The process has finished execution. 13

Questions Using working on a lab assignment as an example What corresponds to running? What corresponds to waiting? What corresponds to ready? 14

So What Is A Process? It s one executing instance of a program It s separated from other instances It can start ( launch ) other processes It can be launched by other processes 15

What Does This Program Do? int myval; int main(int argc, char *argv[]) { myval = atoi(argv[1]); while (1) printf( myval is %d, loc 0x%lx\n, myval, (long) &myval); } Now simultaneously start two instances of this program myval 5 myval 6 What will the outputs be? 16

Here s The Output 17

Instances Of Programs The address was always the same The values were different Implies that the processes aren t seeing each other But they think they re using the same address Conclusion: addresses are not absolute/physical Implication: memory mapping What s the benefit? 18

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 19

Remember This? Application Libraries Portable OS Layer User space/level Kernel space/level Machine-dependent layer 20

Address Space (1) One (common) approach Kernel is high memory User is low memory 0xffff. Kernel space What restrictions apply? read(f, buf, nbytes) User space 0x0000 21

Address Space (2) Program segments Text Data Stack Heap What is text? What is data? What is stack? What is heap? 0xffff. Kernel space User space 0x0000 22

One Common Layout Lots of flexibility Allows stack growth Allows heap growth No predetermined division 0xffff. Kernel space Stack Heap Code & Data 0x0000 23

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 24

Remember This? 25

Process Scheduling Queues Job queue: set of all processes in the system Ready queue: set of all processes residing in main memory, ready and waiting to execute Device queues: set of processes waiting for an I/O device Processes migrate among the various queues 26

Process Scheduling 27

Schedulers Long-term scheduler (or job scheduler) Selects which processes should be brought into the ready queue Invoked very infrequently (seconds, minutes) Þ (may be slow) Controls the degree of multiprogramming Should balance different types of processes: I/O-bound process: spends more time doing I/O than computations, many short CPU bursts CPU-bound process: spends more time doing computations; few very long CPU bursts Short-term scheduler (or CPU scheduler) Selects which process should be executed next and allocates CPU Invoked very frequently (milliseconds) Þ (must be fast) 28

Addition of Medium Term Scheduling 29

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 30

Context Switch Switch CPU from one process to another Performed by scheduler (dispatcher) It includes: Save PCB state of the old process; Load PCB state of the new process; Flush memory cache; Change memory mapping (TLB); Context switch is expensive (1 1000 µs) No useful work is done (pure overhead) Can become a bottleneck Real life analogy? 31

CPU Switch From Process to Process runnin g 32

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 33

Process Creation System initialization Reboot Process creation System call: fork() Users request to create a new process Command line or click an icon Initiation of a batch job Cron Try crontab or at 34

Process Termination Normal exit (voluntary) End of main() Error exit (voluntary) exit(2) Fatal error (involuntary) Divide by 0, core dump Killed by another process (involuntary) kill procid, end task 35

Process Hierarchies Parent creates a child process, a child process can create its own processes 36

Unix Process Related System Calls int fork(void); A new process is created that is an exact copy of the process making the system call, i.e., a copy of the calling process is made and it runs as a new process. The copy is of the memory image of the calling process at the moment of the fork system call, not the program the calling process was started from. The new process does not start at the beginning but at the exact point of the fork system call. Thus, right after the fork there are two processes (the issuing process and newly created process) with identical memory images The return value to the parent is the process identifier of the new process. The return value to the child process is 0. 37

Processes after fork() parent parent fork() child Before fork() After fork() 38

Unix Process Related System Calls int execv(char *programname, char *argv[]); The program programname is loaded in the calling process address space. Thus, the old program in the calling process is overwritten and will no longer exist. The arguments are in the argument vector argv, which is an array of strings, that is, an array of pointers to characters. (There are 6 versions of exec system call) void exit(int returncode); This system call causes a process to exit. The returncode is returned to the parent process if it waits for its child process to terminate. int wait(int *returncode); This system call will cause the calling process to wait until any process created by the calling process exits. The return value is the process identifier of the process that exited. The return code is stored in returncode. 39

Unix Processes: Example 1 What s the functionality of the following code snippet? ProgA { int x; char *arg[1]={0}; x = fork(); if (x==0) execv("progb",arg); exit(3) } 40

Unix Processes: Example 2 Write C code for a process A which creates another process with code from ProgB file, then the process A waits for its child process to terminate, before it exits. ProgA { int x,y,z; char *arg[1]={0}; x=fork(); if (x==0) execv("progb",arg); y=wait(&z); exit(3) } ProgB { // - exit(5); /*point A*/ // - exit(1); /*point B*/ } If the child process exits at point A, then z=5, while if it exits at point B then z=1. 41

Unix Processes: Example 3 Example from Figure 3.10 in the textbook; it illustrates how Unix commands (e.g., ls command) can be issued from a program. void main (int argc, char *argv []) { int pid; pid = fork (); /* fork another process*/ } if (pid <0) { /* error*/ fprintf (stderr, Fork failed ); exit(-1); } else if (pid == 0) { /* child process */ execlp ( /bin/ls, ls, NULL); } else { /* parent process */ wait(null) ; /* waits for child to terminate printf ( Child completed ); exit(0); } 42

Unix Processes: Example 4 Write C code for a process A which creates another process to execute code from file gcc (a compiler) with a list of 3 parameters passed. Then the process A waits for its child process to terminate, before it exits. ProgA { int x,y,z; char *argv[4]={"gcc","-c","namefiletocompile", 0}; } x = fork(); if (x==0) execv("gcc",argv); y = wait(&z); exit(0); 43

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 44

Cooperating Processes Independent process cannot affect or be affected by the execution of another process Cooperating process can affect or be affected by the execution of another process Why cooperating? Information sharing Computation speed-up Modularity Convenience 45

Example: Producer-Consumer Problem Paradigm for cooperating processes: producer process produces information that is consumed by a consumer process Producer Consumer 46

Inter-Process Communication (IPC) Mechanisms for processes to communicate and to synchronize their actions Shared Memory Systems A region of memory are shared among processes Message-Passing Systems Message exchange for communication Comparison between shared memory and messagepassing Shared memory is more efficient Message-passing is easy for programming More? 47

Communication Models 48

Message-Passing Systems Message system processes communicate with each other without resorting to shared variables IPC facility provides two operations: send(message) message size fixed or variable receive(message) If P and Q wish to communicate, they need to: Establish a communication link between them Exchange messages via send/receive Implementation of communication link Physical (e.g., shared memory, hardware bus) Logical (e.g., logical properties) 49

Implementation Questions How are links established? Can a link be associated with more than two processes? How many links can be there between every pair of communicating processes? What is the capacity of a link? Is the size of a message that the link can accommodate fixed or variable? Is a link unidirectional or bi-directional? 50

Direct Communication Processes must name each other explicitly: send(p, message) send a message to process P receive(q, message) receive a message from process Q Properties of communication link Links are established automatically A link is associated with exactly one pair of communicating processes Between each pair there exists exactly one link The link may be unidirectional, but is usually bi-directional A B 51

Indirect Communication (1) Messages directed and received from mailboxes (also referred to as ports) Each mailbox has a unique ID Processes can communicate only if they share a mailbox Properties of communication link Link established only if processes share a common mailbox A link may be associated with many processes Each pair of processes may share several communication links Link may be unidirectional or bi-directional A C B 52

Indirect Communication (2) Operations Create a new mailbox Send and receive messages through mailbox Destroy a mailbox Primitives are defined as: send(a, message) send a message to mailbox A receive(a, message) receive a message from mailbox A 53

Indirect Communication (3) Mailbox sharing P 1, P 2, and P 3 share mailbox A P 1 sends a message; P 2 and P 3 receive Who gets the message? Solutions Allow a link to be associated with at most two processes Allow only one process at a time to execute a receive operation Allow the system to select arbitrarily the receiver. Sender is notified who the receiver was. 54

Synchronization Message passing may be either blocking or non-blocking Blocking is considered synchronous Blocking send has the sender block until the message is received Blocking receive has the receiver block until a message is available Non-blocking is considered asynchronous Non-blocking send has the sender send the message and continue Non-blocking receive has the receiver receive a valid message or null 55

Buffering Queue of messages attached to the link; implemented in one of the three ways Zero capacity 0 messages Sender must wait for receiver (rendezvous) Bounded capacity finite length of n messages Sender must wait if link full Unbounded capacity infinite length Sender never waits 56

Outline What Is A Process? Process States & PCB Process Memory Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 57

Client-Server Communication Why are IPC mechanisms not enough? Sockets Remote Procedure Calls Remote Method Invocation (Java) 58

Sockets A socket is defined as an endpoint for communication Concatenation of IP address and port The socket 161.25.19.8:1625 refers to port 1625 on host 161.25.19.8 Communication consists between a pair of sockets 59

Socket Communication 60

Remote Procedure Calls Why? Remote procedure call (RPC) abstracts procedure calls between processes on networked systems. Stubs: client-side proxy for the actual procedure on the server. The client-side stub locates the server and marshals the parameters. The server-side stub receives this message, unpacks the marshaled parameters, and performs the procedure on the server. 61

Execution of RPC 62

Remote Method Invocation Remote Method Invocation (RMI) is a Java mechanism similar to RPC. RMI allows a Java program on one machine to invoke a method on a remote object. 63

Marshaling Parameters 64

Summary Process Concepts Process States & PCB Address Space Layout Process Scheduling Context Switch Process Operations Inter-Process Communication Client-Server Communication 65