What Is A Bus? A Bus Is:: Slow Vehicle That Many People Ride Together A Bunch of Wires..

What is a bus?
A Bus is:
s
s s
Slow vehicle that many people ride together

well, true...
a shared communication link a single set of wires used to connect multiple subsystems
A bunch of wires...
Processor Input Control Memory Datapath Output
a Bus is also a fundamental tool for composing large, complex systems

systematic means of abstraction
Datorteknik F1 bild 1
Advantages of Buses
Disadvantage of Buses
I/O Device I/O Device Processor I/O Device I/O Device Memory Processor
I/O Device
I/O Device Memory
Versatility:
New devices can be added easily Peripherals can be moved between computer systems that use the same bus standard
s s
It creates a communication bottleneck

The bandwidth of that bus can limit the maximum I/O throughput
The maximum bus speed is largely limited by:

The length of the bus The number of devices on the bus The need to support a range of devices with: s Widely varying latencies s Widely varying data transfer rates
s s
Low Cost:
A single set of wires is shared in multiple ways
Manage complexity by partitioning the design
The General Organization of a Bus

Bus Master
Master versus Slave

Master issues command Bus Slave
Control Lines Data Lines
Data can go either way
Control lines:
Signal requests and acknowledgments Indicate what type of information is on the data lines
A bus transaction includes two parts:

Issuing the command (and address) Transferring the data request action
Data lines carry information between the source and the destination:
Data and Addresses Complex commands
s s
Master is the one who starts the bus transaction by:

issuing the command (and address)
Slave is the one who responds to the address by:

Sending data to the master if the master ask for data Receiving data from the master if the master wants to send data
Types of Buses
s
Example: Bus Architecture

Processor/Memory Bus
Processor-Memory Bus (design specific)

Short and high speed Only need to match the memory system s Maximize memory-to-processor bandwidth Connects directly to the processor Optimized for cache block transfers
Backplane Bus
Backplane Bus (standard or proprietary)

Backplane: an interconnection structure within the chassis Allow processors, memory, and I/O devices to coexist Cost advantage: one bus for all components
I/O Bus (industry standard)

Usually is lengthy and slower Need to match a wide range of I/O devices Connects to the processor-memory bus or backplane bus
I/O Busses
Example: Motherboard Abit BH6
A Computer System with One Bus: Backplane Bus

Backplane Bus Processor Memory
I/O Devices
s
A single bus (the backplane bus) is used for:

Processor to memory communication Communication between I/O devices and memory
s s s
Advantages: Simple and low cost Disadvantages: slow and the bus can become a major bottleneck Example: IBM PC - AT
A Two-Bus System
Processor Memory Bus Processor Bus Adaptor I/O Bus Bus Adaptor I/O Bus Bus Adaptor I/O Bus Memory Processor
A Three-Bus System
Processor Memory Bus Memory Bus Adaptor Bus Adaptor Backplane Bus Bus Adaptor I/O Bus I/O Bus
I/O buses tap into the processor-memory bus via bus adaptors:
Processor-memory bus: mainly for processor-memory traffic I/O buses: provide expansion slots for I/O devices
s
Apple Macintosh-II
NuBus: Processor, memory, and a few selected I/O devices SCSI Bus: the rest of the I/O devices
s
A small number of backplane buses tap into the processormemory bus

Processor-memory bus is used for processor memory traffic I/O buses are connected to the backplane bus
Advantage: loading on the processor bus is greatly reduced

Processor-Memory Bus
s
Memory Bus
4*32 00xx 01xx 10xx 11xx Each access transfers 128 bits
This bus connects the CPU to RAM

Designed for maximal bandwidth Usually wide, 32 bits or more To further increase bandwidth we use a Cache Burst access between cache and memory, early restart
Cache Miss STALL, Start Burst read from RAM PA[3:2] 1 32 Release Pipe STALL Continue Burst read from RAM PA[3:2] 4 2 3 00xx 01xx 10xx 11xx Each RAM bank is only accessed every fourth cycle on burst read
On Chip Cache (1st level)

CP0 IM DE EX DM Using separate Instruction and Data caches, we can read a Hit simultaneously for both Instruction and Data In this model 1st level caches use virtual address, and must pass TLB on Cache miss Instr Cache Data Cache 1st level cache must be fast Limited area on chip Usually 8-64 kb
What defines a bus?

Transaction Protocol
Timing and Signaling Specification Bunch of Wires Electrical Specification
Physical / Mechanical Characterisics the connectors
Synchronous and Asynchronous Bus

s
Synchronous Bus
s
Synchronous bus:
Includes a clock in the control lines A fixed protocol for communication that is relative to the clock Advantage: involves very little logic and can run very fast Disadvantages: s Every device on the bus must run at the same clock rate s To avoid clock skew, they cannot be long if they are fast It is not clocked It can accommodate a wide range of devices It can be lengthened without worrying about clock skew It requires a handshaking protocol
A single clock controls the protocol

Pros s Simple (one FSM) s Fast Cons s Clock skew limits bus length s All devices work on the same speed (clock)
Asynchronous bus:

Suitable for Processor-Memory Bus
Asynchronous Bus
s
Asynchronous Protocol
s s s
Uses a handshaking to implement a transaction protocol

Pros s Versatile, generic protocols s Dynamic data rate Cons s More complex, two communication FSMs s Slower, (but usually can be made quite fast)
ReadReq DataReady Ack
Master ReadReq Ack Wait for Data
Slave
DataReady Ack
Busses so far
Master Slave Control Lines Address Lines Data Lines
Bus Transaction
s s s
Bus Master: has ability to control the bus, initiates transaction Bus Slave: module activated by the transaction Bus Communication Protocol: specification of sequence of events and timing requirements in transferring information. Asynchronous Bus Transfers: control lines (req, ack) serve to orchestrate sequencing. Synchronous Bus Transfers: sequence relative to common clock.
Arbitration Request Action
Arbitration: Obtaining Access to the Bus

Control: Master initiates requests Bus Master Data can go either way Bus Slave
Bus Arbitration
s s
s s
One of the most important issues in bus design:

How is the bus reserved by a devices that wishes to use it?
Bus Master, (initiator usually the CPU) Slave, (usually the Memory)
Chaos is avoided by a master-slave arrangement:

Only the bus master can control access to the bus: It initiates and controls all bus requests A slave responds to read and write requests
The simplest system:

Processor is the only bus master All bus requests must be controlled by the processor Major drawback: the processor is involved in every transaction
Arbitration signals s BusRequest s BusGrant s BusPriority

Higher priority served first Fairness, no request is locked out
Multiple Potential Bus Masters:

the Need for Arbitration
s s
Bus Arbitration Schemes

Daisy chain arbitration
Grant line runs through all device, highest priority device first. Single device with all request lines. s
Bus arbitration scheme:

A bus master wanting to use the bus asserts the bus request A bus master cannot use the bus until its request is granted A bus master must signal to the arbiter after finish using the bus
Centralized
Many request/grant lines Complex controller, may be a bottleneck
Bus arbitration schemes usually try to balance two factors:

Bus priority: the highest priority device should be serviced first Fairness: Even the lowest priority device should never be completely locked out from the bus
Self Selection
Many request lines The one with highest priority self decides to take bus
Collision Detection (Ethernet)

One request line Try to access bus, If collision device backoff Try again in random + exponential time
The Daisy Chain Bus Arbitrations Scheme

Device 1 Highest Priority Grant Bus Arbiter Grant Device 2 Device N Lowest Priority Grant Release Request
Centralized Parallel Arbitration

Device 1 Device 2 Device N
Grant Bus Arbiter
Req
wired-OR
s s
Advantage: simple Disadvantages:

Cannot assure fairness: A low-priority device may be locked out indefinitely The use of the daisy chain grant signal also limits the bus speed
Used in essentially all processor-memory busses and in highspeed I/O busses

Simplest bus paradigm

BReq BG
Simple Synchronous Protocol
R/W Address Data
Cmd+Addr Data1 Data2
s s s
All agents operate syncronously All can source / sink data at same rate => simple protocol
just manage the source and target
Even memory busses are more complex than this

memory (slave) may take time to respond it need to control data rate
Typical Synchronous Protocol

s
BReq BG R/W Address Wait Cmd+Addr
Increasing the Bus Bandwidth

Separate versus multiplexed address and data lines:
Address and data can be transmitted in one bus cycle if separate address and data lines are available Cost: (a) more bus lines, (b) increased complexity s
Data bus width:

By increasing the width of the data bus, transfers of multiple words require fewer bus cycles Example: SPARCstation 20s memory bus is 128 bit wide Cost: more bus lines
s
Data Data1 Data1 Data2
Block transfers:
Allow the bus to transfer multiple words in back-to-back bus cycles Only one address needs to be sent at the beginning The bus is not released until the last word is transferred Cost: (a) increased complexity (b) increased response time (latency) for request
s s
Slave indicates when it is prepared for data xfer Actual transfer goes at bus rate
Pipelined Bus Protocols

Attempt to initiate next address phase during current data phase
s
Increasing Transaction Rate on Multimaster Bus

Overlapped arbitration
perform arbitration for next transaction during current transaction
s
Single master example (proc-to-cache)
Bus parking
master can holds onto bus and performs multiple transactions as long as no other master makes request
CLK Active
s
Overlapped address / data phases (prev. slide)

requires one of the above techniques
w_l wait data addr

XXX Addr 1 RDATA1 ADDR 2 ADDR 3 RDATA2 WR DATA3
Split-phase transaction bus ( Command queueing)

completely separate address and data phases arbitrate separately for each address phase yield a tag which is matched with data phase
All of the above in most modern mem busses

Split Transaction Protocol

When we dont need the bus, release it!
Improves throughput Increases latency and complexity Master Master ReadReq requests Ack bus
s s
The I/O Bus Problem

s
Slave
Designed to support wide variety of devices

full set not know at design time
No one requests bus Slave requests bus
Allow data rate match between arbitrary speed deviced

fast processor slow I/O slow processor fast I/O
Wait for Data
DataReady Ack
High Speed I/O Bus

Virtual Address
s
Backplane Bus
Bus Adapter Control 2nd level Cache Physical Addr Data Primary Memory RAM CP0 IM DE EX DM 1st level Cache TLB
Examples
Raid controllers Graphics adapter
s s s s
Limited number of devices Data transfer bursts at full rate DMA transfers important
small controller spools stream of bytes to or from memory
Either side may need to stall transfer

buffers fill up
HD Interface Serial Interface Graphics Adapter Sound Card
Direct Memory Access (DMA)

(2) CP0 IM DE EX DM 1st level Cache TLB We want to move data from HD interface to RAM (1) HD Interface Why go all the way to the CPU (1) and back to the memory bus (2)
s
Direct Memory Access

s
RAM 2nd level Cache
DMA Processor
1) Generates BusRequest, waits for Grant 2) Put Address & Data on Bus 3) Increase Address, back to 2 until finished 4) Release Bus
Generates interrupt only

When finished If an error occurred
DMA and Virtual Memory

s
DMA and Caching

s
If DMA uses Virtual address it needs to pass a TLB

Go through the CPUs TLB (no good) A TLB in the DMA processor (needs updating)
INCONSISTENCY problem
We change the RAM contents, but not the cache We write to HD but the RAM holds old information
Routing All DMA though CPU

No good, spoils the idea!
If DMA uses Physical address

Only transfer within one Page We give the DMA a set of Physical addresses s (local TLB copy)
s
Software handling of DMA

Cache: Flush selected cache lines to RAM Cache: Invalidate selected cache lines TLB/OS: Do not allow access to these pages until DMA finished
Hardware Cache Coherence Protocol

Complex, but very useful for multi processor systems
PCI Read/Write Transactions

s s s s s s
PCI Read Transaction
All signals sampled on rising edge Centralized Parallel Arbitration

overlapped with previous transaction
All transfers are (unlimited) bursts Address phase starts by asserting FRAME# Next cycle initiator asserts cmd and address Data transfers happen on when
IRDY# asserted by master/initiator when ready to transfer data TRDY# asserted by target when ready to transfer data transfer when both asserted on rising edge
FRAME# deasserted when master intends to complete only one more data transfer
Turn-around cycle on any signal driven by more than one agent
Datorteknik F1 bild 43 Datorteknik F1 bild 44
PCI Write Transaction

s
PCI Optimizations
Push bus efficiency toward 100% under common simple usage
like RISC
s
Bus Parking
retain bus grant for previous master until another makes request granted master can start next transfer without arbitration
Arbitrary Burst length

intiator and target can exert flow control with xRDY target can disconnect request with STOP (abort or retry) master can disconnect by deasserting FRAME arbiter can disconnect by deasserting GNT
Delayed (pended, split-phase) transactions

free the bus after request to slow device
Additional PCI Issues

sOption
Summary of Bus Options

High performance Separate address & data lines Wider is faster (e.g., 32 bits) Multiple words has less bus overhead Multiple (requires arbitration) Synchronous pipelined Low cost Multiplex address & data lines Narrower is cheaper (e.g., 8 bits) Single-word transfer is simpler Single master (no arbitration) Asynchronous Serial
s s s s
Interrupts: support for controlling I/O devices Cache coherency:

support for I/O and multiprocessors
sBus sData
width width size
Locks:
support timesharing, I/O, and MPs
sTransfer sBus
Configuration Address Space
masters
sClocking sProtocol

What Is A Bus? A Bus Is:: Slow Vehicle That Many People Ride Together A Bunch of Wires..

Uploaded by

What Is A Bus? A Bus Is:: Slow Vehicle That Many People Ride Together A Bunch of Wires..

Uploaded by

What is a bus?

Slow vehicle that many people ride together

a Bus is also a fundamental tool for composing large, complex systems

I/O Device Memory

It creates a communication bottleneck

The maximum bus speed is largely limited by:

Manage complexity by partitioning the design

The General Organization of a Bus

Master versus Slave

Control Lines Data Lines

Data can go either way

A bus transaction includes two parts:

Master is the one who starts the bus transaction by:

Slave is the one who responds to the address by:

Example: Bus Architecture

Processor-Memory Bus (design specific)

Backplane Bus (standard or proprietary)

I/O Bus (industry standard)

Example: Motherboard Abit BH6

A Computer System with One Bus: Backplane Bus

A single bus (the backplane bus) is used for:

A small number of backplane buses tap into the processormemory bus

Advantage: loading on the processor bus is greatly reduced

This bus connects the CPU to RAM

On Chip Cache (1st level)

What defines a bus?

Timing and Signaling Specification Bunch of Wires Electrical Specification

Physical / Mechanical Characterisics the connectors

Synchronous and Asynchronous Bus

A single clock controls the protocol

Suitable for Processor-Memory Bus

Uses a handshaking to implement a transaction protocol

ReadReq DataReady Ack

Master ReadReq Ack Wait for Data

Arbitration Request Action

Arbitration: Obtaining Access to the Bus

One of the most important issues in bus design:

Chaos is avoided by a master-slave arrangement:

The simplest system:

Arbitration signals s BusRequest s BusGrant s BusPriority

Multiple Potential Bus Masters:

Bus Arbitration Schemes

Bus arbitration scheme:

Bus arbitration schemes usually try to balance two factors:

Collision Detection (Ethernet)

The Daisy Chain Bus Arbitrations Scheme

Centralized Parallel Arbitration

Grant Bus Arbiter

Advantage: simple Disadvantages:

Used in essentially all processor-memory busses and in highspeed I/O busses

Simplest bus paradigm

Simple Synchronous Protocol

R/W Address Data

Cmd+Addr Data1 Data2

Even memory busses are more complex than this

Typical Synchronous Protocol

Increasing the Bus Bandwidth

Data bus width:

Pipelined Bus Protocols

Increasing Transaction Rate on Multimaster Bus

Single master example (proc-to-cache)

Overlapped address / data phases (prev. slide)

w_l wait data addr

Split-phase transaction bus ( Command queueing)

All of the above in most modern mem busses

Split Transaction Protocol

The I/O Bus Problem

Designed to support wide variety of devices

No one requests bus Slave requests bus

Allow data rate match between arbitrary speed deviced

Wait for Data

High Speed I/O Bus

Either side may need to stall transfer

HD Interface Serial Interface Graphics Adapter Sound Card

Direct Memory Access (DMA)

Direct Memory Access