ch07 input/output
DESCRIPTION
CH07 Input/Output. External Devices I/O Modules Programmed I/O Interrupt-Driven I/O Direct Memory Access I/O Channels and Processor The External Interface: SCSI and FireWire. TECH Computer Science. CH06. Input/Output Problems. Wide variety of peripherals - PowerPoint PPT PresentationTRANSCRIPT
![Page 1: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/1.jpg)
CH07 Input/Output
• External Devices• I/O Modules• Programmed I/O• Interrupt-Driven I/O• Direct Memory Access• I/O Channels and Processor• The External Interface: SCSI and FireWire
CH06
TECH Computer Science
![Page 2: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/2.jpg)
Input/Output Problems
• Wide variety of peripheralsDelivering different amounts of dataAt different speeds In different formats
• All slower than CPU and RAM• Need I/O modules
![Page 3: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/3.jpg)
Input/Output Module
• Interface to CPU and Memory• Interface to one or more peripherals• GENERIC MODEL OF I/O DIAGRAM 6.1
![Page 4: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/4.jpg)
Generic Model of an I/O Module
![Page 5: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/5.jpg)
External Devices
• Human readableScreen, printer, keyboard
• Machine readableMonitoring and control
• CommunicationModemNetwork Interface Card (NIC)
![Page 6: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/6.jpg)
I/O Module Function
• Control & Timing• CPU Communication• Device Communication• Data Buffering• Error Detection
![Page 7: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/7.jpg)
I/O Steps
• CPU checks I/O module device status• I/O module returns status• If ready, CPU requests data transfer• I/O module gets data from device• I/O module transfers data to CPU• Variations for output, DMA, etc.
![Page 8: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/8.jpg)
I/O Module Diagram
Data Register
Status/Control Register
ExternalDeviceInterfaceLogic
ExternalDeviceInterfaceLogic
InputOutputLogic
DataLines
AddressLines
DataLines
Data
Status
Control
Data
Status
Control
Systems Bus Interface External Device Interface
![Page 9: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/9.jpg)
I/O Module Decisions
• Hide or reveal device properties to CPU• Support multiple or single device• Control device functions or leave for CPU• Also O/S decisions
e.g. Unix treats everything it can as a file
![Page 10: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/10.jpg)
Input Output Techniques
• Programmed• Interrupt driven• Direct Memory Access (DMA)
![Page 11: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/11.jpg)
Three I/O Techniques
![Page 12: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/12.jpg)
Programmed I/O
• CPU has direct control over I/OSensing statusRead/write commandsTransferring data
• CPU waits for I/O module to complete operation• Wastes CPU time
![Page 13: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/13.jpg)
Programmed I/O - detail
• CPU requests I/O operation• I/O module performs operation• I/O module sets status bits• CPU checks status bits periodically• I/O module does not inform CPU directly• I/O module does not interrupt CPU• CPU may wait or come back later
![Page 14: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/14.jpg)
I/O Commands
• CPU issues address Identifies module (& device if >1 per module)
• CPU issues commandControl - telling module what to do
e.g. spin up disk
Test - check statuse.g. power? Error?
Read/WriteModule transfers data via buffer from/to device
![Page 15: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/15.jpg)
Addressing I/O Devices
• Under programmed I/O data transfer is very like memory access (CPU viewpoint)
• Each device given unique identifier
• CPU commands contain identifier (address)
![Page 16: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/16.jpg)
I/O Mapping
• Memory mapped I/ODevices and memory share an address space I/O looks just like memory read/writeNo special commands for I/O
Large selection of memory access commands available
• Isolated I/OSeparate address spacesNeed I/O or memory select linesSpecial commands for I/O
Limited set
![Page 17: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/17.jpg)
Interrupt Driven I/O
• Overcomes CPU waiting• No repeated CPU checking of device• I/O module interrupts when ready
![Page 18: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/18.jpg)
Simple Interrupt Processing
![Page 19: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/19.jpg)
Interrupt Driven I/OBasic Operation
• CPU issues read command• I/O module gets data from peripheral whilst CPU
does other work• I/O module interrupts CPU• CPU requests data• I/O module transfers data
![Page 20: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/20.jpg)
CPU Viewpoint
• Issue read command• Do other work• Check for interrupt at end of each instruction cycle• If interrupted:-
Save context (registers)Process interrupt
Fetch data & store
• See Operating Systems notes
![Page 21: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/21.jpg)
Design Issues //
• How do you identify the module issuing the interrupt?• How do you deal with multiple interrupts?
i.e. an interrupt handler being interrupted
![Page 22: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/22.jpg)
Identifying Interrupting Module (1)
• Different line for each modulePCLimits number of devices
• Software pollCPU asks each module in turnSlow
![Page 23: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/23.jpg)
Identifying Interrupting Module (2)
• Daisy Chain or Hardware poll Interrupt Acknowledge sent down a chainModule responsible places vector on busCPU uses vector to identify handler routine
• Bus MasterModule must claim the bus before it can raise interrupt e.g. PCI & SCSI
![Page 24: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/24.jpg)
Multiple Interrupts
• Each interrupt line has a priority• Higher priority lines can interrupt lower priority lines• If bus mastering only current master can interrupt
![Page 25: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/25.jpg)
Example - PC Bus
• 80x86 has one interrupt line• 8086 based systems use one 8259A interrupt
controller• 8259A has 8 interrupt lines
![Page 26: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/26.jpg)
Sequence of Events
• 8259A accepts interrupts• 8259A determines priority• 8259A signals 8086 (raises INTR line)• CPU Acknowledges• 8259A puts correct vector on data bus• CPU processes interrupt
![Page 27: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/27.jpg)
PC Interrupt Layout
8086
INTR
8259A
IRQ0IRQ1IRQ2IRQ3IRQ4IRQ5IRQ6IRQ7
CPU
I/O Module
![Page 28: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/28.jpg)
ISA Bus Interrupt System
• ISA bus chains two 8259As together• Link is via interrupt 2• Gives 15 lines
16 lines less one for link
• IRQ 9 is used to re-route anything trying to use IRQ 2Backwards compatibility
• Incorporated in chip set
![Page 29: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/29.jpg)
ISA Interrupt Layout
80x86
INTR
8259A
IRQ0IRQ1IRQ2IRQ3IRQ4IRQ5IRQ6IRQ7
8259A
IRQ0 (8)IRQ1 (9)IRQ2 (10)IRQ3 (11)IRQ4 (12)IRQ5 (13)IRQ6 (14)IRQ7 (15)
(IRQ 2)
![Page 30: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/30.jpg)
Foreground Reading //• http://www.pcguide.com/ref/mbsys/res/irq/func.htm
• In fact look at http://www.pcguide.com/
![Page 31: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/31.jpg)
Direct Memory Access
• Interrupt driven and programmed I/O require active CPU interventionTransfer rate is limitedCPU is tied up
• DMA is the answer
![Page 32: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/32.jpg)
DMA Function
• Additional Module (hardware) on bus• DMA controller takes over from CPU for I/O
![Page 33: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/33.jpg)
DMA Operation
• CPU tells DMA controller:-Read/WriteDevice addressStarting address of memory block for dataAmount of data to be transferred
• CPU carries on with other work• DMA controller deals with transfer• DMA controller sends interrupt when finished
![Page 34: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/34.jpg)
DMA TransferCycle Stealing
• DMA controller takes over bus for a cycle• Transfer of one word of data• Not an interrupt
CPU does not switch context
• CPU suspended just before it accesses bus i.e. before an operand or data fetch or a data write
• Slows down CPU but not as much as CPU doing transfer
![Page 35: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/35.jpg)
DMA Configurations (1)
• Single Bus, Detached DMA controller• Each transfer uses bus twice
I/O to DMA then DMA to memory
• CPU is suspended twice
CPUDMAController
I/ODevice
I/ODevice
Main Memory
![Page 36: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/36.jpg)
DMA Configurations (2)
• Single Bus, Integrated DMA controller• Controller may support >1 device• Each transfer uses bus once
DMA to memory
• CPU is suspended once
CPUDMAController
I/ODevice
I/ODevice
Main Memory
DMAController
I/ODevice
![Page 37: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/37.jpg)
DMA Configurations (3)
• Separate I/O Bus• Bus supports all DMA enabled devices• Each transfer uses bus once
DMA to memory
• CPU is suspended once
CPU DMAController
I/ODevice
I/ODevice
Main Memory
I/ODevice
I/ODevice
![Page 38: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/38.jpg)
I/O Channels
• I/O devices getting more sophisticated e.g. 3D graphics cards
• CPU instructs I/O controller to do transfer• I/O controller does entire transfer• Improves speed
Takes load off CPUDedicated processor is faster
![Page 39: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/39.jpg)
6.7 External Interfacing
• Connecting external devices together• Bit of wire?• Parallel interface; e.g. parallel port, SCSI• Serial interface; e.g. serial port, FireWire• Point-to-point; e.g. keyboard, modem, display• Multipoint; SCSI, FireWire, USB, (Bus)
![Page 40: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/40.jpg)
Small Computer Systems Interface (SCSI)
• Parallel interface• 8, 16, 32 bit data lines• Daisy chained; host7~d0~d1~…d6~T• Drive 7 has highest priority• Devices are independent• Devices can communicate with each other as well as
host
![Page 41: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/41.jpg)
Configuring SCSI
• Bus must be terminated at each endUsually one end is host adapterPlug in terminator or switch(es)
• SCSI Id must be setJumpers or switchesUnique on chain0 (zero) for boot deviceHigher number is higher priority in arbitration
![Page 42: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/42.jpg)
SCSI - 1
• Early 1980s• 8 bit• 5MHz• Data rate 5MBytes.s-1
• Seven devicesEight including host interface
![Page 43: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/43.jpg)
SCSI - 2
• 1991• 16 and 32 bit• 10MHz• Data rate 20 or 40 Mbytes.s-1
• (Check out Ultra/Wide SCSI)
![Page 44: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/44.jpg)
SCSI Signaling (1)
• Between initiator and targetUsually host & device
• Bus free? (c.f. Ethernet)• Arbitration - take control of bus (c.f. PCI)• Select target• Reselection
Allows reconnection after suspension e.g. if request takes time to execute, bus can be released
![Page 45: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/45.jpg)
SCSI Signaling (2)
• Command - target requesting from initiator• Data request• Status request• Message request (both ways)
![Page 46: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/46.jpg)
SCSI Bus Phases
ArbitrationBus free (Re)Selection
Command,Data, Status,Message
Reset
![Page 47: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/47.jpg)
SCSI Timing Diagram
![Page 48: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/48.jpg)
SCSI Read e.g. (transfer data from target to initiator)
• (1) ArbitrationEach device asserts BSY and one of data lines (0,1,2,…7
highest), highest priority wins Winner is the initiator
• (2) Selection phase Initiator asserts SEL, its own ID, target ID Initiator negates BSYTarget recognizes its ID, it assets the BSY Initiator release the data bus and negates SEL
![Page 49: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/49.jpg)
SCSI Read e.g. cont…
• (3) Command phaseTarget asserts C/D, then asserts REQ Initiator places first byte of the command and asserts
ACKTarget reads the command, then negates REQ Initiator then negates ACK (this first command contains operation code and how
many bytes remain to be transferred.)Use the same REQ and ACK handshaking to transfer
the remaining bytes. (in this e.g. the command is a Read; transfer data from
target to initiator
![Page 50: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/50.jpg)
SCSI Read e.g. cont…
• (4) Data phaseAfter interpreted the command, target negate C/D
(means data bus contains data), it asserts I/O (means direction of transfer is target to initiator)
Target places the first byte of data on the bus, asserts the REQ
Initiator reads the byte and asserts ACKThe remaining data transfer using REQ and ACK
handshaking
![Page 51: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/51.jpg)
SCSI Read e.g. cont…
• (5) Status phaseTarget asserts C/D, and remains asserting I/OUse REQ and ACK handshaking to transfer
successfully transfer, (no problem)
• (6) Message PhaseTarget asserts MSG, places “Command Complete”
message on the bus, use REQ and ACKTarget received ACK from initiator, then release all bus
signals and negates BSY (Done!)
![Page 52: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/52.jpg)
IEEE 1394 FireWire //
• High performance serial bus• Fast• Low cost• Easy to implement• Also being used in digital cameras, VCRs and TV• Sony call this bus I-link.
![Page 53: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/53.jpg)
FireWire Configuration
• Daisy chain• Up to 63 devices on single port
Really 64 of which one is the interface itself
• Up to 1022 buses can be connected with bridges• May be tree structure• Hot plugging• Automatic configuration• No bus terminators
![Page 54: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/54.jpg)
FireWire 3 Layer Stack
• PhysicalTransmission medium, electrical and signaling
characteristics
• LinkTransmission of data in packets
• TransactionRequest-response protocol
![Page 55: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/55.jpg)
FireWire - Physical Layer
• Data rates from 25 to 400Mbps• Two forms of arbitration
Based on tree structureRoot acts as arbiterFirst come first servedNatural priority controls simultaneous requests
i.e. who is nearest to root
Fair arbitration (time for using bus by fairness intervals)
Urgent arbitration (urgent device may use up to 75% of the bus time)
![Page 56: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/56.jpg)
FireWire - Link Layer
• Transmission of data in the from of packets• Two transmission types
AsynchronousVariable amount of data and several bytes of transaction data
transferred as a packetTo explicit addressAcknowledgement returned
IsochronousVariable amount of data in sequence of fixed size packets at regular
intervalsSimplified addressingNo acknowledgement
![Page 57: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/57.jpg)
FireWire – Transaction Layer
• Define a request-response protocol that hides the lower-layer details of FireWire from applications
• E.g. TCP/IP
![Page 58: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/58.jpg)
Foreground Reading
• Check out Universal Serial Bus (USB)• Compare with other communication standards e.g.
Ethernet
![Page 59: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/59.jpg)
Exercises
• Check up on-line slide show on:• www.laTech.edu/~choi• Read CH 6• Do Problems:
3.14.2 & 4.95.1
• Due BY Email to: [email protected]
• Due by Wednesday
![Page 60: CH07 Input/Output](https://reader035.vdocuments.mx/reader035/viewer/2022062301/56812ce3550346895d91a96a/html5/thumbnails/60.jpg)