Cheating the IO Bottleneck Network Storage with.pptVIP

Processes, Unix, and IPC Today Welcome back Midterm scores are on the Web; Lab #4 is where you left it. Today we continue with process management topics. last time: address space creation/initialization today: process interactions and synchronization Exec/Exit/Join synchronization (midterm problem #4) A peek at the Unix process model, its strengths and limitations Start on mechanisms for Interprocess Communication (IPC) IPC mechanisms combine synchronization and data transfer pipes, streams, messages, Remote Procedure Call (RPC) Midterm Results Process Internals Nachos Exec/Exit/Join Example Process Management Example(Midterm Problem #4) Process Birth Example(Midterm Problem #4) Process Join Example(Midterm Problem #4) Process Death Example(Midterm Problem #4) Elements of the Unix Process and I/O Model 1. rich model for IPC and I/O: “everything is a file” file descriptors: most/all interactions with the outside world are through system calls to read/write from file descriptors, with a unified set of syscalls for operating on open descriptors of different types. 2. simple and powerful primitives for creating and initializing child processes fork: easy to use, expensive to implement 3. general support for combining small simple programs to perform complex tasks standard I/O and pipelines: good programs don’t know/care where their input comes from or where their output goes Unix File Descriptors Unix processes name I/O and IPC objects by integers known as file descriptors. File descriptors 0, 1, and 2 are reserved by convention for standard input, standard output, and standard error. “Conforming” Unix programs read input from stdin, write output to stdout, and errors to stderr by default. Other descriptors are assigned by syscalls to open/create files, create pipes, or bind to devices or network sockets. pipe, socket, open, creat A common set of syscalls operate on open file descriptors independent of their underlying types. read, write, dup, close Unix File De