UNIT 6 - Input Output Management.ppt

INPUT OUTPUT (IO) MANAGEMENT By Dr D B Ntalasha Introduction Humans interact with machines by providing information through IO devices. Many on-line services are availed through use of specialized devices like printers, keyboards etc. Management of these devices can affec...

INPUT OUTPUT (IO) MANAGEMENT By Dr D B Ntalasha Introduction Humans interact with machines by providing information through IO devices. Many on-line services are availed through use of specialized devices like printers, keyboards etc. Management of these devices can affect the throughput of a system. A Typical PC Bus Structure Issues in IO Management Communication with an IO device is required at the following levels: The need for a human to input information and output from a computer. The need for a device to input information and receive output from a computer. The need for computers to communicate over networks. Device Speeds Character oriented input devices operate with speeds of tens of bytes per second. Block oriented devices are much faster than character oriented devices. Also note that they operate over a much wider range. Devices communicate bit or byte streams with a machine using a data bus and a device controller. Event Based I/O -1 A computer system may have to synchronize with some other process to communicate. So, one process may actually wait at the point of rendezvous for the other process to arrive. The process advances further following the synchronizing event Event Based I/O -2 Processes may use signals to communicate events. Processes may wait for asynchronous events to occur. Every OS provides a set of mechanisms which may be like polling, or a programmed data transfer, or an interrupt mechanism, or even use DMA with cycle stealing. IO Organization -1 Computers employ the four basic modes of IO operation: These are: 1. Polling 2. Programmed mode 3. Interrupt mode 4. DMA mode Polling Polling: Computer interrogates each device in turn to determine if it is ready to communicate. Polling as a strategy is also used by systems to interrogate ports on a computer communication network Example For each byte of I/O 1. Read busy bit from status register until 0 2. Host sets read or write bit and if write copies data into data-out register 3. Host sets command-ready bit 4. Controller sets busy bit, executes transfer 5. Controller clears busy bit, error bit, command-ready bit when transfer done Step 1 is busy-wait cycle to wait for I/O from device  Reasonable if device is fast  But inefficient if device slow  CPU switches to other tasks?  But if miss a cycle data overwritten / lost Programmed mode Programmed mode : An IO instruction is issued to a device. Now the program busy-waits (idles) till the device IO is completed. In other words execution of I/O instruction is in sequence with other program instructions. Interrupt mode Interrupt mode : An IO instruction is issued. The program advances without suspension till the device is actually ready to establish an IO, when the process is suspended. Interrupts Polling can happen in 3 instruction cycles Read status, logical-and to extract status bit, branch if not zero How to be more efficient if non-zero infrequently? CPU Interrupt-request line triggered by I/O device Checked by processor after each instruction Interrupt handler receives interrupts Maskable to ignore or delay some interrupts Interrupt vector to dispatch interrupt to correct handler Context switch at start and end Based on priority Some nonmaskable Interrupt chaining if more than one device at same interrupt number Interrupt-Driven I/O Cycle DMA mode DMA mode : The device requests for an IO for a block data transfer. The execution is briefly suspended and the starting address and size of data block are stored in a DMA controller. Direct Memory Access Used to avoid programmed I/O (one byte at a time) for large data movement Requires DMA controller Bypasses CPU to transfer data directly between I/O device and memory OS writes DMA command block into memory Source and destination addresses Read or write mode Count of bytes Writes location of command block to DMA controller Bus mastering of DMA controller – grabs bus from CPU Cycle stealing from CPU but still much more efficient When done, interrupts to signal completion Version that is aware of virtual addresses can be even more efficient - DVMA Six Step Process to Perform DMA Transfer Network oriented traffic Network oriented traffic can be handled in DMA mode. Network traffic usually corresponds to getting information from a disc file at both ends and network traffic is bursty. In all the above modes, OS makes it look as if we are doing a read or a write operation on a file. Interrupt Mode - 1 In this mode, an IO instruction is issued and the program advances without suspension. Program suspension happens when the device is actually ready to establish an IO. An Interrupt Service Routine is executed to achieve device IO. Interrupt Mode -2 Process context is stored to help resume computation later (from the point of suspension.) Program resumes execution from where it was suspended. Interrupt types -1 Interrupt processing may require the following contexts : Internal Interrupt : Source of interrupt is a memory resident process or an event within a processor (due to divide by zero or attempt to execute an illegal instruction). Some times malfunctions caused by events like divide by zero are called traps. Timer interrupts may also occur as in RTOSs. Interrupt types - 2 External Interrupts : Source of interrupt is not internal i.e. other than a process or processor related event. Can be caused by a device seeking attention of a processor. IO device interrupting a program that had sought IO (mentioned earlier) is an external interrupt. Interrupt types - 3 Software Interrupt : Most OSs offer two modes of operation – user mode and system mode. A system call made by a user program will require a transition from user mode to system mode – this generates a software interrupt. Hardware Support to Recognize Interrupt Interrupt Servicing -1 Let us see how an interrupt is serviced : Suppose program P is executing an instruction i when an interrupt is raised. Assume also an interrupt service routine ISR to be initiated to service the interrupt. Interrupt Servicing -2 The following steps describe how the interrupt service may happen : 1. Suspend the current program P after executing instruction i. 2. Store address of instruction i+1 in P as return address for P – PADDRi+1 which is the incremented program counter value. This may be stored (RESTORE) in some specific location or a systems’ data structure or in the code area of ISR itself. Interrupt Servicing -3 3. A branch unconditionally to interrupt service instructions in ISR happens. 4. Typically, the last instruction in the service routine ISR executes a branch indirect from RESTORE. This restores the program counter a branch indirect instruction from PADDRi+1 Thus the suspended program P obtains control of the processor again. Identification of Source of Interrupts -1 We will see how source of interrupt may be identified in the context of different I/O mechanisms like: Polling : It interrogates all the devices in sequence It is slow if there are many devices Identification of Source of Interrupts -2 Identification of Source of Interrupts -3 I/O and the Kernel -1 Usually, an OS kernel resolves IO commands. Following an issuance of an IO command, the kernel communicates with individual device drivers; which in turn communicate with IO devices. The application at the top level communicates only with the kernel. I/O and the Kernel -2 Each IO request from an application generates the following: Naming or identification of the device to communicate. Providing device independent data to communicate. I/O and the Kernel -3 I/O and the Kernel -4 Kernel IO subsystem arranges for the following: Identification of the device driver. Allocation of buffers. Reporting of errors. Tracking the device usage. I/O and the Kernel -5 The device driver transfers the kernel IO request to set device controller with the following information : Identify read/write request. Set controller registers for data transfer (Data count = 0; where to locate data) Keep track when the data has been transferred (when fresh data is to be brought in). Device Driver Operation The figure below shows the sequence which device drivers follow to handle interrupts: Management Buffer -1 Example in the figure shows how at different stages the buffer sizes may differ. Management of Buffers - 2 Buffers are usually set up in the main memory or in caches. Caches are used to obtain enhanced performance. Buffers absorb mismatch in the data transfer rates of the processor or memory on one side and the device on the other. Management of Buffers - 3 Assume we are seeking input of data from a device. The various buffering strategies are as follows: Single buffer : The device first fills a buffer. Next the device driver hands in its control to the kernel to input the data in the buffer. Once the buffer has been used up, the device fills it up again for input. Management of Buffers - 4 Double buffer : Here there are 2 buffers. Device driver starts by filling buffer-0 and then hands it to the kernel to be emptied. In the meanwhile it starts to fill buffer-1. The roles are switched when buffer-1 is filled out. Management of Buffers - 5 Circular buffer : One can say that double buffer is a circular queue of size 2. We can have many buffers in a circular queue. Kernel accesses filled out buffers in the same order that these are filled out. Note that buffer management requires management of a queue data structure. One must have pointers to the head and tail of this queue to determine if it is full or empty Additional Considerations Spooling in Printers Consider a printer connected to a machine and several users wanting to use it. To avoid print clashes, all the print requests are SPOOLED and thus the requests are queued. OS maintains and schedules all print requests. We can examine print queue status with lpq and lpstat commands in Unix. Additional Considerations Clocks and Management of Time -1 Clocks : CPU has a system clock. OS uses this clock to provide a variety of system and application based services such as : Maintaining time of day (date command in Unix) Scheduling a program run at a specified time during systems’ operation (cron command) Additional Considerations Clocks and Management of Time -2 Providing over runs by processes in preemptive scheduling - important for real-time systems. Keeping track of resource utilization or reserving resource use. Performance related measurements (like timing IO, CPU activity). Additional Considerations Identifying Devices Addressing a device : Most OSs reserve some address space for use as exclusive addresses for devices (like DMA controllers, timer, serial ports). Each of them have fixed ranges of addresses so that they communicate with the right ports of data. Additional Considerations Caching -1 A cache is an intermediate level fast storage. Caches are regarded as fast buffers. Caching may be between disk and memory or memory and CPU. It helps in overcoming the latency during an instruction fetch. It helps in higher locality of reference when used for data Additional Considerations Caching -1 As for main memory to disk caches, one use is in disk rewrites. This technique is used almost always to collect all write requests over a short period of time and subsequently it is actually written into disc. Caching is always done to enhance the performance of systems. Additional Considerations IO channels : an IO channel is primarily a small computer to basically handle IO from multiple sources – smoothes out IO traffic. OS and CDE : OS provides several terminal oriented facilities for operations in a Common Desktop Environment. IO kernel provides all screen management functions within the frame work of a CDE. Motivation for Disc Scheduling Primary memory is volatile and secondary memory is non- volatile. Primary memory loses its information when power goes off; unlike secondary memory. The most common secondary storage is a disc. Comparison of Policies -1 FCFS Policy : The service is provided strictly in the sequence in which the requests arrived. The service would be in the sequence : 59, 41, 172, 74, 52, 85, 139, 12, 194 and 87. In order to compare the effect of implementing a certain policy, we analyze the arm movements – captures the basic disc activity. The end Questions