hila
Uploaded by
7 SLIDES
214 VIEWS
70LIKES

Understanding I/O Procedures in Operating Systems: Handling User Requests Efficiently

DESCRIPTION

This article explores the intricate I/O procedures within operating systems, focusing on how user processes request input/output operations. The DOIO system call parameters include device identification, mode of operation, and data transfer amounts. The article describes how requests are assembled into I/O request blocks and queued, managed by a dedicated device handler process. It explains the cycle of request handling, including error checks, signaling operations, and semaphore synchronization, ensuring efficient and reliable I/O processing.

1 / 7

Download Presentation

Understanding I/O Procedures in Operating Systems: Handling User Requests Efficiently

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. I/O Procedures

  2. I/O Procedures • We shall now consider how the operating system handles a request for I/O from a user process. • A request from a process will be a system call to the operating system of the form. • DOIO( device, mode, amount, destination, semaphore)

  3. I/O Procedures contd… • DOIO is the name of a system I/O procedure. • Device is the number of the device on which the I/O operation will take place. • Mode indicates the operation and sometimes the character code to be used. • Amount amount of data to be transferred. • Destination location into which the transfer is to occur • Semaphore is the address of a semaphore request serviced

  4. I/O Procedures contd… • The I/O procedure assembles the parameters of the request into an I/O request block and adds it to the I/O request queue. • The I/O request queue is associated to the descriptor of the concerned device and is serviced by a separate process called device handler.

  5. I/O Procedures contd… • The I/O procedure notifies the device handler that a request has been placed on the I/O request queue by the request pending signal and when the operation is complete the device handler notifies the user by the means of requestserviced . • A device handler operates in a continuous cycle during which it removes an IORB from the request queue initiates the corresponding I/O operation and waits for that operation to be completed.

  6. I/O Procedures contd… Next device in device structure DESTINATION IDENTIFICATION QUALITY STATUS MODE Originating process CHARACTERISTICS Semaphore request serviced DEVICE REQUEST QUEUE Error location Translation tables CURRENT IORB IORB SEMAPHORE Request pending Process descriptor of current user Remainder of request serviced SEMAPHORE Operation complete DEVICE DESCRIPTOR

  7. Sketch of I/O system I/O Procedure Device Handler Interrupt routine User DOIO (device, mode, semaphore, amount, destination); Identify device; perform error checks; assemble IORB; place IORB on device request queue; signal( request pending); Wait (request pending); pick IORB from request queue; Initiate I/O; wait (operation complete); Locate device descriptor; Signal (operation complete); perform error checks; performance error checks; perform housekeeping; signal( request serviced); delete IORB wait ( request serviced ); test error location exit; Flow of Control Semaphore synchronization

More Related
SlideServe
Audio
Live Player
Audio Wave
Play slide audio to activate visualizer