Introduction (Processes and Files)

Slides:



Advertisements
Similar presentations
Slide 2-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 2 Using the Operating System 2.
Advertisements

CSC 501 Lecture 2: Processes. Von Neumann Model Both program and data reside in memory Execution stages in CPU: Fetch instruction Decode instruction Execute.
Slide 6-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 6 Implementing Processes, Threads, and Resources.
The Process Model.
1 Processes Professor Jennifer Rexford
1 Processes and Pipes COS 217 Professor Jennifer Rexford.
Processes CSCI 444/544 Operating Systems Fall 2008.
Page 1 Processes and Threads Chapter 2. Page 2 Processes The Process Model Multiprogramming of four programs Conceptual model of 4 independent, sequential.
Using the OS. Basic Abstractions Idea Program Result Idea Program Result Program Result … …
1 CS 333 Introduction to Operating Systems Class 2 – OS-Related Hardware & Software The Process Concept Jonathan Walpole Computer Science Portland State.
Process Management. External View of the OS Hardware fork() CreateProcess() CreateThread() close() CloseHandle() sleep() semctl() signal() SetWaitableTimer()
Advanced OS Chapter 3p2 Sections 3.4 / 3.5. Interrupts These enable software to respond to signals from hardware. The set of instructions to be executed.
Process in Unix, Linux and Windows CS-3013 C-term Processes in Unix, Linux, and Windows CS-3013 Operating Systems (Slides include materials from.
CS-502 Fall 2006Processes in Unix, Linux, & Windows 1 Processes in Unix, Linux, and Windows CS502 Operating Systems.
Chapter 2: Using the Operating System. The Airplane Pilot’s Abstract Machine.
Unix & Windows Processes 1 CS502 Spring 2006 Unix/Windows Processes.
Chapter 6 Implementing Processes, Threads, and Resources.
© 2004, D. J. Foreman 2-1 Concurrency, Processes and Threads.
Slide 6-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 6.
Processes in Unix, Linux, and Windows CS-502 Fall Processes in Unix, Linux, and Windows CS502 Operating Systems (Slides include materials from Operating.
Slide 3-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 3.
The Programming Interface. Main Points Creating and managing processes – fork, exec, wait Performing I/O – open, read, write, close Communicating between.
Slide 6-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 6.
Process in Unix, Linux, and Windows CS-3013 A-term Processes in Unix, Linux, and Windows CS-3013 Operating Systems (Slides include materials from.
CSC 501 Lecture 2: Processes. Process Process is a running program a program in execution an “instantiation” of a program Program is a bunch of instructions.
Threads, Thread management & Resource Management.
Today’s Topics Introducing process: the basic mechanism for concurrent programming –Process management related system calls Process creation Process termination.
Processes and Threads CS550 Operating Systems. Processes and Threads These exist only at execution time They have fast state changes -> in memory and.
Lecture 3 Process Concepts. What is a Process? A process is the dynamic execution context of an executing program. Several processes may run concurrently,
Hardware process When the computer is powered up, it begins to execute fetch-execute cycle for the program that is stored in memory at the boot strap entry.
Threads.
Slide 3-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 3.
ITEC 502 컴퓨터 시스템 및 실습 Chapter 2-1: Process Mi-Jung Choi DPNM Lab. Dept. of CSE, POSTECH.
System calls for Process management
 For an application programmer, the operating system interface is most important  The functions provided by the OS  Abstract resources that are available.
Slide 6-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 6 Implementing Processes, Threads, and Resources 6.
CS4315A. Berrached:CMS:UHD1 Process Management Chapter 6.
1 Computer Systems II Introduction to Processes. 2 First Two Major Computer System Evolution Steps Led to the idea of multiprogramming (multiple concurrent.
Fall 2002 CS 325 Class Notes Page 1 Lecture 25 Today –exec() in Unix –CreateProcess in Windows Announcements.
Threads, Thread management & Resource Management.
Hardware process When the computer is powered up, it begins to execute fetch-execute cycle for the program that is stored in memory at the boot strap entry.
STRUCTURE OPERATING SYSTEMS. I. PROCESS MANAGEMENT Process a program in execution More than one process can be associated with a single program Each is.
2 Processor(s)Main MemoryDevices Process, Thread & Resource Manager Memory Manager Device Manager File Manager.
What is a Process ? A program in execution.
System calls for Process management Process creation, termination, waiting.
Slide 2-1 Copyright © 2004 Pearson Education, Inc. Operating Systems: A Modern Perspective, Chapter 2.
2.1 Processes  process = abstraction of a running program  multiprogramming = CPU switches from running program to running program  pseudoparallelism.
CSCI/CMPE 4334 Operating Systems Review: Exam 1 1.
Chapter 3 The Programming Interface Chien-Chung Shen CIS/UD
A process is a program in execution A running system consists of multiple processes – OS processes Processes started by the OS to do “system things” –
Protection of System Resources
Concurrency, Processes and Threads
Operating Systems: A Modern Perspective, Chapter 6
Chapter 3: Processes.
Processes in Unix, Linux, and Windows
Using the Operating System
Processes in Unix, Linux, and Windows
Tutorial: The Programming Interface
Concurrency, Processes and Threads
Operating Systems: A Modern Perspective, Chapter 3
CSE 451: Operating Systems Winter 2003 Lecture 4 Processes
Processes in Unix, Linux, and Windows
Implementing Processes, Threads, and Resources
Processes in Unix and Windows
CSE 451: Operating Systems Autumn 2004 Module 4 Processes
Outline Process Management Process manager Hardware process
CSE 153 Design of Operating Systems Winter 2019
Concurrency, Processes and Threads
Implementing Processes, Threads, and Resources
Presentation transcript:

Introduction (Processes and Files) Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Basic Abstractions Idea Program Result Idea Program Result … … Idea Program Result Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Basic Abstractions(2) Idea Abstract Machine Program Result Physical Machine Idea Abstract Machine Program Result … … Idea Abstract Machine Program Result Operating Systems: A Modern Perspective, Chapter 2

Abstract Machine Entities Process: A sequential program in execution Resource: Any abstract resource that a process can request, and which may can cause the process to be blocked if the resource is unavailable. File: A special case of a resource. A linearly-addressed sequence of bytes. “A byte stream.” Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Processes Operating Systems: A Modern Perspective, Chapter 2

Algorithms, Programs, and Processes Idea Execution Engine Files Algorithm Stack Status Source Program Binary Program Data Other Resources Process Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Classic Process OS implements {abstract machine} – one per task Multiprogramming enables N programs to be space-muxed in executable memory, and time-muxed across the physical machine processor. Result: Have an environment in which there can be multiple programs in execution concurrently*, each as a processes * Concurrently: Programs appear to execute simultaneously Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Process Abstraction Data Process Program Stack Operating System Processor Hardware Executable Memory Operating Systems: A Modern Perspective, Chapter 2

Processes Sharing a Program Files P1 P2 P3 P1 Files P2 Files P3 Shared Program Text Operating Systems: A Modern Perspective, Chapter 2

Modern Process & Thread Divide classic process: Process is an infrastructure in which execution takes place – address space + resources Thread is a program in execution within a process context – each thread has its own stack Stack Data Thread Thread Stack Process … Program Stack Thread Operating System Operating Systems: A Modern Perspective, Chapter 2

A Process with Multiple Threads Thread (Execution Engine) Stack Status Files Stack Status Data Stack Status Other Resources Binary Program Process Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 More on Processes Abstraction of processor resource Programmer sees an abstract machine environment with spectrum of resources and a set of resource addresses (most of the addresses are memory addresses) User perspective is that its program is the only one in execution OS perspective is that it runs one program with its resources for a while, then switches to a different process (context switching) OS maintains A process descriptor data structure to implement the process abstraction Identity, owner, things it owns/accesses, etc. Tangible element of a process Resource descriptors for each resource Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Address Space Process must be able to reference every resource in its abstract machine Assign each unit of resource an address Most addresses are for memory locations Abstract device registers Mechanisms to manipulate resources Addresses used by one process are inaccessible to other processes Say that each process has its own address space Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Shared Address Space Classic processes sharing program  shared address space support Thread model simplifies the problem All threads in a process implicitly use that process’s address space , but no “unrelated threads” have access to the address space Now trivial for threads to share a program and data If you want sharing, encode your work as threads in a process If you do not want sharing, place threads in separate processes Operating Systems: A Modern Perspective, Chapter 2

Process & Address Space Resources Data Resources Code Resources Stack Abstract Machine Environment Address Space Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Creating a Process Here is the classic model for creating processes: FORK(label): Create another process in the same address space beginning execution at instruction label QUIT(): Terminate the process. JOIN(count): disableInterrupts(); count--; if(count > 0) QUIT(); enableInterrupts(); Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 UNIX Processes Files Stack Segment Status Text Segment Data Segment Other Resources Process UNIX Kernel Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 UNIX Processes Each process has its own address space Subdivided into text, data, & stack segment a.out file describes the address space OS kernel creates descriptor to manage process Process identifier (PID): User handle for the process (descriptor) Try “ps” and “ps -aux” (read man page) Operating Systems: A Modern Perspective, Chapter 2

Creating/Destroying Processes UNIX fork() creates a process Creates a new address space Copies text, data, & stack into new adress space Provides child with access to open files UNIX wait() allows a parent to wait for a child to terminate UNIX execa() allows a child to run a new program Operating Systems: A Modern Perspective, Chapter 2

Creating a UNIX Process int pidValue; ... pidValue = fork(); /* Creates a child process */ if(pidValue == 0) { /* pidValue is 0 for child, nonzero for parent */ /* The child executes this code concurrently with parent */ childsPlay(…); /* A procedure linked into a.out */ exit(0); } /* The parent executes this code concurrently with child */ parentsWork(..); wait(…); Operating Systems: A Modern Perspective, Chapter 2

Child Executes a Different Program int pid; ... /* Set up the argv array for the child */ /* Create the child */ if((pid = fork()) == 0) { /* The child executes its own absolute program */ execve(childProgram.out, argv, 0); /* Only return from an execve call if it fails */ printf(“Error in the exec … terminating the child …”); exit(0); } wait(…); /* Parent waits for child to terminate */ Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Example: Parent #include <sys/wait.h> #define NULL 0 int main (void) { if (fork() == 0){ /* This is the child process */ execve("child",NULL,NULL); exit(0); /* Should never get here, terminate */ } /* Parent code here */ printf("Process[%d]: Parent in execution ...\n", getpid()); sleep(2); if(wait(NULL) > 0) /* Child terminating */ printf("Process[%d]: Parent detects terminating child \n", getpid()); printf("Process[%d]: Parent terminating ...\n", getpid()); Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Example: Child int main (void) { /* The child process's new program This program replaces the parent's program */ printf("Process[%d]: child in execution ...\n", getpid()); sleep(1); printf("Process[%d]: child terminating ...\n", getpid()); } Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Threads -- The NT Model Thread (Execution Engine) Stack Status Files Stack Status Data Stack Status Other Resources Binary Program Process Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Windows NT Process #include <cthreads.h> ... int main(int argv, char *argv[]) { STARTUPINFO startInfo; PROCESS_INFORMATION processInfo; strcpy(lpCommandLine, “C:\\WINNT\\SYSTEM32\\NOTEPAD.EXE temp.txt)”; ZeroMemory(&startInfo, sizeof(startInfo)); startInfo.cb = sizeof(startInfo); if(!CreateProcess(NULL, lpCommandLine, NULL, NULL, FALSE, HIGH_PRIORITY_CLASS | CREATE_NEW_CONSOLE, NULL, NULL, &startInfo, &processInfo)) { fprintf(stderr, “CreateProcess failed on error %d\n”, GetLastError()); ExitProcess(1); }; /* A new child process is now executing the lpCommandLine program */ CloseHandle(&processInfo.hThread); CloseHandle(&processInfo.hProcess); t_handle = CreateProcess(…, lpCommandLine, …); } Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 NT Threads #include <cthreads.h> ... int main(int argv, char *argv[]) { t_handle = CreateThread( LPSECURITY_ATTRIBUTES lpThreadAttributes, // pointer to thread security attributes DWORD dwStackSize, // initial thread stack size, in bytes LPTHREAD_START_ROUTINE lpStartAddress, // pointer to thread function LPVOID lpParameter, // argument for new thread DWORD dwCreationFlags, // creation flags LPDWORD lpThreadId // pointer to returned thread identifier ); /* A new child thread is now executing the tChild function */ Sleep(100) /* Let another thread execute */ } DWPRD WINAPI tChild(LPVOID me) { /* This function is executed by the child thread */ SLEEP(100); /* Let another thread execute */ Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 _beginthreadex() Single copy of certain variables in a process Need a copy per thread unsigned long _beginthreadex( void *security, unsigned stack_size, unsigned ( __stdcall *start_address )( void * ), void *arglist, unsigned initflag, unsigned *thrdaddr ); Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Resources Anything that a process requests from an OS Available  allocated Not available  process is blocked Examples Files Primary memory address space (“virtual memory”) Actual primary memory (“physical memory”) Devices (e.g., window, mouse, kbd, serial port, …) Network port … many others … Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 Files Data must be read into (and out of) the machine – I/O devices Storage devices provide persistent copy Need an abstraction to make I/O simple – the file A file is a linearly-addressed sequence of bytes From/to an input device Including a storage device Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 The File Abstraction Data File Process Program Stack Operating System File Descriptor Processor Storage Device Hardware Executable Memory Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 UNIX Files UNIX and NT try to make every resource (except CPU and RAM) look like a file Then can use a common interface: open Specifies file name to be used close Release file descriptor read Input a block of information write Output a block of information lseek Position file for read/write ioctl Device-specific operations Operating Systems: A Modern Perspective, Chapter 2

Operating Systems: A Modern Perspective, Chapter 2 UNIX File Example #include <stdio.h> #include <fcntl.h> int main() { int inFile, outFile; char *inFileName = “in_test”; char *outFileName = “out_test”; int len; char c; inFile = open(inFileName, O_RDONLY); outFile = open(outFileName, O_WRONLY); /* Loop through the input file */ while ((len = read(inFile, &c, 1)) > 0) write(outFile, &c, 1); /* Close files and quite */ close(inFile); close(outFile); } Operating Systems: A Modern Perspective, Chapter 2

Windows File Manipulation Program #include <windows.h> #include <stdio.h> #define BUFFER_LEN ... // # of bytes to read/write /* The producer process reads information from the file name in_test then writes it to the file named out_test. */ int main(int argc, char *argv[]) { // Local variables char buffer[BUFFER_LEN+1]; // CreateFile parameters DWORD dwShareMode = 0; // share mode LPSECURITY_ATTRIBUTES lpFileSecurityAttributes = NULL; // pointer to security attributes HANDLE hTemplateFile = NULL; // handle to file with attributes to copy // ReadFile parameters HANDLE sourceFile; // Source of pipeline DWORD numberOfBytesRead; // number of bytes read LPOVERLAPPED lpOverlapped = NULL; // Not used here Operating Systems: A Modern Perspective, Chapter 2

Windows File Manipulation Program(2) // WriteFile parameters HANDLE sinkFile; // Source of pipeline DWORD numberOfBytesWritten; // # bytes written // Open the source file sourceFile = CreateFile ( "in_test", GENERIC_READ, dwShareMode, lpFileSecurityAttributes, OPEN_ALWAYS, FILE_ATTRIBUTE_READONLY, hTemplateFile ); if(sourceFile == INVALID_HANDLE_VALUE) { fprintf(stderr, "File open operation failed\n"); ExitProcess(1); } Operating Systems: A Modern Perspective, Chapter 2

Windows File Manipulation Program(3) // Open the sink file sinkFile = CreateFile ( "out_test", GENERIC_WRITE, dwShareMode, lpSecurityAttributes, CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, hTemplateFile ); if(sinkFile == INVALID_HANDLE_VALUE) { fprintf(stderr, "File open operation failed\n"); ExitProcess(1); } Operating Systems: A Modern Perspective, Chapter 2

Windows File Manipulation Program(4) // Main loop to copy the file while ( ReadFile( sourceFile, buffer, BUFFER_LEN, &numberOfBytesRead, lpOverlapped ) && numberOfBytesRead > 0 ) { WriteFile(sinkFile, buffer, BUFFER_LEN, &numberOfBytesWritten, lpOverlapped); } // Terminating. Close the sink and source files CloseHandle(sourceFile); CloseHandle(sinkFile); ExitProcess(0); Operating Systems: A Modern Perspective, Chapter 2