Chapter05 Input Output

Input/Output
Chapter 5
Tanenbaum & Bos, Modern Operating Systems: 4th ed., Global Edition (c) 2015 Pearson Education Limited. All rights reserved.
I/O Devices (1)
• Block devices
– Stores information in fixed-size blocks
– Transfers are in units of entire blocks
• Character devices
– Delivers or accepts stream of characters, without regard to block
structure
– Not addressable, does not have any seek operation
I/O Devices (2)
Figure 5-1. Some

typical device,
network, and bus
data rates.
Memory-Mapped I/O (1)
Figure 5-2. (a) Separate I/O and memory space.

(b) Memory-mapped I/O. (c) Hybrid.
Memory-Mapped I/O (2)
Figure 5-3. (a) A single-bus architecture.

(b) A dual-bus memory architecture.
Direct Memory Access
Figure 5-4. Operation of a DMA transfer.
Interrupts Revisited
Figure 5-5. How an interrupt happens. The connections between

the devices and the interrupt controller actually use interrupt
lines on the bus rather than dedicated wires.
Precise Interrupt
Four properties of a precise interrupt:
1. The PC saved in a known place.
2. All instructions before that pointed to by PC have fully
executed.
3. No instruction beyond that pointed to by PC has been
executed.
4. Execution state of instruction pointed to by PC is known.
Precise vs. Imprecise
Figure 5-6. (a) A precise interrupt. (b) An imprecise interrupt.
Goals of the I/O Software
Issues:
• Device independence
• Uniform naming
• Error handling
• Synchronous versus asynchronous
• Buffering.
Programmed I/O (1)
Figure 5-7. Steps in printing a string.
Programmed I/O (2)
Figure 5-8. Writing a string to the printer

using programmed I/O.
Interrupt-Driven I/O
Figure 5-9. Writing a string to the printer using interrupt-

driven I/O. (a) Code executed at the time the print system
call is made. (b) Interrupt service procedure for the printer.
I/O Using DMA
Figure 5-10. Printing a string using DMA. (a) Code executed when
the print system call is made. (b) Interrupt service procedure.
I/O Software Layers
Figure 5-11. Layers of the I/O software system.
Interrupt Handlers (1)
Typical steps after hardware interrupt completes:
1. Save registers (including the PSW) not already saved
by interrupt hardware.
2. Set up context for interrupt service procedure.
3. Set up a stack for the interrupt service procedure.
4. Acknowledge interrupt controller. If no centralized
interrupt controller, reenable interrupts.
5. Copy registers from where saved to process table.
Interrupt Handlers (2)
Typical steps after hardware interrupt completes:
6. Run interrupt service procedure. Extract
information from interrupting device controller’s
registers.
7. Choose which process to run next.
8. Set up the MMU context for process to run next.
9. Load new process’ registers, including its PSW.
10. Start running the new process.
Device Drivers
Figure 5-12. Logical positioning of device drivers.

In reality all communication between drivers
and device controllers goes over the bus.
Device-Independent I/O Software
Figure 5-13. Functions of the

device-independent I/O software.
Uniform Interfacing
for Device Drivers
Figure 5-14. (a) Without a standard driver interface.

(b) With a standard driver interface.
Buffering (1)
Figure 5-15. (a) Unbuffered input. (b) Buffering in user space.

(c) Buffering in the kernel followed by copying to user space.
(d) Double buffering in the kernel.
Buffering (2)
Figure 5-16. Networking may involve many

copies of a packet.
User-Space I/O Software
Figure 5-17. Layers of the I/O system and

the main functions of each layer.
Magnetic Disks (1)
Figure 5-18. Disk parameters for the original IBM PC 360-KB floppy
disk and a Western Digital WD 3000 HLFS (‘‘Velociraptor’’) hard disk.
Magnetic Disks (2)
Figure 5-19. (a) Physical geometry of a disk with two zones.

(b) A possible virtual geometry for this disk.
RAID (1)
Figure 5-20. RAID

levels 0 through 3.
Backup and parity
drives are shown
shaded.
RAID (2)
Figure 5-20. RAID

levels 4 through 6.
Backup and parity
drives are shown
shaded.
Disk Formatting (1)
Figure 5-21. A disk sector.
Disk Formatting (2)
Figure 5-22. An illustration of cylinder skew.

Disk Formatting (3)
Figure 5-23. (a) No interleaving. (b) Single interleaving.

(c) Double interleaving.
Disk Arm Scheduling Algorithms (1)
Factors of a disk block read/write:
1. Seek time (the time to move the arm to
the proper cylinder).
2. Rotational delay (how long for the proper
sector to come under the head).
3. Actual data transfer time.
Figure 5-24. Shortest Seek First (SSF) disk scheduling algorithm.
Figure 5-25. The elevator algorithm for scheduling disk requests.
Error Handling
Figure 5-26. (a) A disk track with a bad sector. (b) Substituting
a spare for the bad sector. (c) Shifting all the sectors to
bypass the bad one.
Stable Storage (1)
• Uses pair of identical disks
• Either can be read to get same results
• Operations defined to accomplish this:
1. Stable Writes
2. Stable Reads
3. Crash recovery
Stable Storage (2)
Figure 5-27. Analysis of the influence of crashes on stable writes.
Clock Hardware
Figure 5-28. A programmable clock.
Clock Software (1)
Typical duties of a clock driver:
1. Maintaining the time of day.
2. Preventing processes from running longer than allowed.
3. Accounting for CPU usage.
4. Handling alarm system call from user processes.
5. Providing watchdog timers for parts of system itself.
6. Profiling, monitoring, statistics gathering.
Clock Software (2)
Figure 5-29. Three ways to maintain the time of day.
Clock Software (3)
Figure 5-30. Simulating multiple timers with a single clock.
Soft Timers
Soft timers stand or fall with the rate at which kernel entries are
made for other reasons. These reasons include:
1. System calls.
2. TLB misses.
3. Page faults.
4. I/O interrupts.
5. The CPU going idle.
Keyboard Software
Figure 5-31. Characters that are handled

specially in canonical mode.
Output Software – Text Windows
Figure 5-32. The ANSI escape sequences accepted by the terminal

driver on output. ESC denotes the ASCII escape character (0x1B),
and n, m, and s are optional numeric parameters.
The X Window System (1)
Figure 5-33. Clients and servers in the M.I.T. X Window System.

Types of messages between client and server:
1. Drawing commands from program to workstation.
2. Replies by workstation to program queries.
3. Keyboard, mouse, and other event announcements.
4. Error messages.
Figure 5-34. A skeleton of an X Window application program.
Figure 5-34. A skeleton of an X Window application program.
Graphical User Interfaces (1)
Figure 5-35. A sample window located at (200, 100)

on an XGA display.
Figure 5-36. A skeleton of a Windows main program.
Figure 5-36. A skeleton of a Windows main program.
Figure 5-37. An example rectangle drawn using Rectangle.

Each box represents one pixel.
Bitmaps
Figure 5-38. Copying bitmaps using BitBlt.

(a) Before. (b) After.
Fonts
Figure 5-39. Some examples of character outlines

at different point sizes.
Hardware Issues
Figure 5-40. Power consumption of various

parts of a notebook computer.
Operating System Issues
The Display
Figure 5-41. The use of zones for backlighting the display.

(a) When window 2 is selected it is not moved.
(b) When window 1 is selected, it moves to reduce the
number of zones illuminated.
Operating System Issues
The CPU
Figure 5-42. (a) Running at full clock speed. (b) Cutting

voltage by two cuts clock speed by two and power
consumption by four
End
Chapter 5

Chapter05 Input Output

Uploaded by

Copyright:

Available Formats

Chapter05 Input Output

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Chapter05 Input Output

Uploaded by

Copyright:

Available Formats

Input/Output

Figure 5-1. Some

Figure 5-2. (a) Separate I/O and memory space.

Figure 5-3. (a) A single-bus architecture.

Figure 5-4. Operation of a DMA transfer.

Figure 5-5. How an interrupt happens. The connections between

Figure 5-6. (a) A precise interrupt. (b) An imprecise interrupt.

Figure 5-7. Steps in printing a string.

Figure 5-8. Writing a string to the printer

Figure 5-9. Writing a string to the printer using interrupt-

Figure 5-11. Layers of the I/O software system.

Figure 5-12. Logical positioning of device drivers.

Figure 5-13. Functions of the

Figure 5-14. (a) Without a standard driver interface.

Figure 5-15. (a) Unbuffered input. (b) Buffering in user space.

Figure 5-16. Networking may involve many

Figure 5-17. Layers of the I/O system and

Figure 5-19. (a) Physical geometry of a disk with two zones.

Figure 5-20. RAID

Figure 5-20. RAID

Figure 5-21. A disk sector.

Figure 5-22. An illustration of cylinder skew.

Figure 5-23. (a) No interleaving. (b) Single interleaving.

Figure 5-24. Shortest Seek First (SSF) disk scheduling algorithm.

Figure 5-25. The elevator algorithm for scheduling disk requests.

Figure 5-27. Analysis of the influence of crashes on stable writes.

Figure 5-28. A programmable clock.

Figure 5-29. Three ways to maintain the time of day.

Figure 5-30. Simulating multiple timers with a single clock.

Figure 5-31. Characters that are handled

Figure 5-32. The ANSI escape sequences accepted by the terminal

Figure 5-33. Clients and servers in the M.I.T. X Window System.

Figure 5-34. A skeleton of an X Window application program.

Figure 5-34. A skeleton of an X Window application program.

Figure 5-35. A sample window located at (200, 100)

Figure 5-36. A skeleton of a Windows main program.

Figure 5-36. A skeleton of a Windows main program.

Figure 5-37. An example rectangle drawn using Rectangle.

Figure 5-38. Copying bitmaps using BitBlt.

Figure 5-39. Some examples of character outlines

Figure 5-40. Power consumption of various

Figure 5-41. The use of zones for backlighting the display.

Figure 5-42. (a) Running at full clock speed. (b) Cutting

You might also like