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

Similar documents
Chapter 4: Processes. Process Concept

Chapter 4: Processes

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

Chapter 4: Processes

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

Chapter 4: Processes. Process Concept

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

Part Two - Process Management. Chapter 3: Processes

Diagram of Process State Process Control Block (PCB)

The Big Picture So Far. Chapter 4: Processes

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

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

The Big Picture So Far. Chapter 4: Processes

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

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

Chapter 4: Processes. Process Concept. Process State

Chapter 3: Processes

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

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

Chapter 4: Processes

Chapter 3: Process Concept

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

Lecture 2 Process Management

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

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

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

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

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

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

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

Chapter 3: Processes. Operating System Concepts 9 th Edition

CHAPTER 3 - PROCESS CONCEPT

Chapter 3: Processes. Operating System Concepts 8th Edition

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

Chapter 3: Processes

Chapter 3: Process Concept

Chapter 3: Process Concept

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

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

Chapter 3: Process Concept

Chapter 3: Process Concept

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

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

Chapter 3: Processes. Operating System Concepts 9 th Edition

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

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

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

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

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

CS307 Operating Systems Processes

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

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

Chapter 3: Processes

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

Processes. Process Concept

CSI Module 2: Processes

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

Processes and Threads

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

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

CS370 Operating Systems

Course: Operating Systems Instructor: M Umair. M Umair

Chapter 3: Processes

CS420: Operating Systems. Interprocess Communication

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

ICS Principles of Operating Systems

CSC 539: Operating Systems Structure and Design. Spring 2006

CHAPTER 2: PROCESS MANAGEMENT

CS370 Operating Systems

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.

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

Chapter 3: Processes. Operating System Concepts 9 th Edit9on

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

PROCESS MANAGEMENT. Operating Systems 2015 Spring by Euiseong Seo

UNIT - II PROCESS MANAGEMENT

Operating System Design

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

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

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

Killing Zombies, Working, Sleeping, and Spawning Children

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

Processes. Operating System Concepts 8 th Edition

Processes. Rafael Ramirez Dep Tecnologia Universitat Pompeu Fabra

CSCE 313: Intro to Computer Systems

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

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

Interprocess Communication

CSCE 313 Introduction to Computer Systems. Instructor: Dezhen Song

Processes CHAPTER CHAPTER OBJECTIVES. 3.1 Process Concept

Operating System Concepts Ch. 3: Processes

Operating Systems. Lecture 05

Ricardo Rocha. Department of Computer Science Faculty of Sciences University of Porto

Reading Assignment 4. n Chapter 4 Threads, due 2/7. 1/31/13 CSE325 - Processes 1

Dept. Of Computer Science, Colorado State University

Frequently asked questions from the previous class survey

Process! Process Creation / Termination! Process Transitions in" the Two-State Process Model! A Two-State Process Model!

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.

Transcription:

Processes Process Concept Process Scheduling Operations on Processes Cooperating Processes Interprocess Communication Communication in Client-Server Systems 4.1 Sana a University, Dr aimen

Process Concept An operating system executes a variety of programs: Batch system jobs Time-shared systems user programs or tasks Textbook uses the terms job and process almost interchangeably Process a program in execution; process execution must progress in sequential fashion A process includes: program counter stack data section 4.2 Sana a University, Dr aimen

Process State As a process executes, it changes state new: The process is being created running: Instructions are being executed waiting: The process is waiting for some event to occur ready: The process is waiting to be assigned to a process terminated: The process has finished execution 4.3 Sana a University, Dr aimen

Diagram of Process State 4.4 Sana a University, Dr aimen

Process Control Block (PCB) Information associated with each process Process state Program counter CPU registers CPU scheduling information Memory-management information Accounting information I/O status information 4.5 Sana a University, Dr aimen

Process Control Block (PCB) 4.6 Sana a University, Dr aimen

CPU Switch From Process to Process 4.7 Sana a University, Dr aimen

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 Process migration between the various queues 4.8 Sana a University, Dr aimen

Ready Queue And Various I/O Device Queues 4.9 Sana a University, Dr aimen

Representation of Process Scheduling 4.10 Sana a University, Dr aimen

Schedulers Long-term scheduler (or job scheduler) selects which processes should be brought into the ready queue Short-term scheduler (or CPU scheduler) selects which process should be executed next and allocates CPU 4.11 Sana a University, Dr aimen

Addition of Medium Term Scheduling 4.12 Sana a University, Dr aimen

Schedulers (Cont.) Short-term scheduler is invoked very frequently (milliseconds) (must be fast) Long-term scheduler is invoked very infrequently (seconds, minutes) (may be slow) The long-term scheduler controls the degree of multiprogramming Processes can be described as either: 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 4.13 Sana a University, Dr aimen

Context Switch When CPU switches to another process, the system must save the state of the old process and load the saved state for the new process Context-switch time is overhead; the system does no useful work while switching Time dependent on hardware support 4.14 Sana a University, Dr aimen

Process Creation Parent process create children processes, which, in turn create other processes, forming a tree of processes Resource sharing Parent and children share all resources Children share subset of parent s resources Parent and child share no resources Execution Parent and children execute concurrently Parent waits until children terminate 4.15 Sana a University, Dr aimen

Address space Process Creation (Cont.) Child duplicate of parent Child has a program loaded into it UNIX examples fork system call creates new process exec system call used after a fork to replace the process memory space with a new program 4.16 Sana a University, Dr aimen

C Program Forking Separate Process #include <stdio.h> #include <unistd.h> int main(int argc, char *argv[]) { int pid; /* fork another process */ pid = fork(); if (pid < 0) { /* error occurred */ fprintf(stderr, "Fork Failed"); exit(-1); } else if (pid == 0) { /* child process */ execlp("/bin/ls","ls",null); } else { /* parent process */ /* parent will wait for the child to complete */ wait(null); printf("child Complete"); exit(0); } } 4.17 Sana a University, Dr aimen

Process Termination Process executes last statement and asks the operating system to decide it (exit) Output data from child to parent (via wait) Process resources are deallocated by operating system Parent may terminate execution of children processes (abort) Child has exceeded allocated resources Task assigned to child is no longer required If parent is exiting Some operating system do not allow child to continue if its parent terminates All children terminated - cascading termination 4.18 Sana a University, Dr aimen

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 Advantages of process cooperation Information sharing Computation speed-up Modularity Convenience 4.19 Sana a University, Dr aimen

Producer-Consumer Problem Paradigm for cooperating processes, producer process produces information that is consumed by a consumer process unbounded-buffer places no practical limit on the size of the buffer bounded-buffer assumes that there is a fixed buffer size 4.20 Sana a University, Dr aimen

Bounded-Buffer Buffer Shared-Memory Solution public interface Buffer { // producers call this method public abstract void insert(object item); // consumers call this method public abstract Object remove(); } 4.21 Sana a University, Dr aimen

Bounded-Buffer Buffer Shared Memory Solution import java.util.*; public class BoundedBuffer implements Buffer { private static final int BUFFER SIZE = 5; private int count; // number of items in the buffer private int in; // points to the next free position private int out; // points to the next full position private Object[] buffer; public BoundedBuffer() { // buffer is initially empty count = 0; in = 0; out = 0; buffer = new Object[BUFFER SIZE]; } // producers calls this method public void insert(object item) { // Slide 4.24 } // consumers calls this method public Object remove() { // Figure 4.25 } } 4.22 Sana a University, Dr aimen

Bounded-Buffer Buffer Insert() Method public void insert(object item) { while (count == BUFFER SIZE) ; // do nothing -- no free buffers // add an item to the buffer ++count; buffer[in] = item; in = (in + 1) % BUFFER SIZE; } 4.23 Sana a University, Dr aimen

Bounded Buffer Remove() Method public Object remove() { Object item; while (count == 0) ; // do nothing -- nothing to consume // remove an item from the buffer --count; item = buffer[out]; out = (out + 1) % BUFFER SIZE; return item; } 4.24 Sana a University, Dr aimen

Interprocess Communication (IPC) Mechanism for processes to communicate and to synchronize their actions 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) 4.25 Sana a University, Dr aimen

Implementation Questions How are links established? Can a link be associated with more than two processes? How many links can there be 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? 4.26 Sana a University, Dr aimen

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 4.27 Sana a University, Dr aimen

Indirect Communication Messages are 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 4.28 Sana a University, Dr aimen

Indirect Communication 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 4.29 Sana a University, Dr aimen

Mailbox sharing Indirect Communication P 1, P 2, and P 3 share mailbox A P 1, sends; 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. 4.30 Sana a University, Dr aimen

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 4.31 Sana a University, Dr aimen

Buffering Queue of messages attached to the link; implemented in one of three ways 1. Zero capacity 0 messages Sender must wait for receiver (rendezvous) 2. Bounded capacity finite length of n messages Sender must wait if link full 3. Unbounded capacity infinite length Sender never waits 4.32 Sana a University, Dr aimen

Sockets Client-Server Communication Remote Procedure Calls Remote Method Invocation (Java) 4.33 Sana a University, Dr aimen

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 4.34 Sana a University, Dr aimen

Socket Communication 4.35 Sana a University, Dr aimen

Remote Procedure Calls 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 marshalls the parameters. The server-side stub receives this message, unpacks the marshalled parameters, and peforms the procedure on the server. 4.36 Sana a University, Dr aimen

Execution of RPC 4.37 Sana a University, Dr aimen

Remote Method Invocation Remote Method Invocation (RMI) is a Java mechanism similar to RPCs. RMI allows a Java program on one machine to invoke a method on a remote object. 4.38 Sana a University, Dr aimen