Computer Organization and Architecture - Chapter 1: Introduction pot

Architecture & Organization 1• Architecture is those attributes visible to the programmer — Instruction set, number of bits used for data representation, I/O mechanisms, addressing techn

William Stallings

Computer Organization and Architecture

7th Edition

Chapter 1

Introduction

Architecture & Organization 1

• Architecture is those attributes visible to the programmer

— Instruction set, number of bits used for data representation, I/O mechanisms, addressing techniques.

— e.g Is there a multiply instruction?

• Organization is how features are

Architecture & Organization 2

• All Intel x86 family share the same basic architecture

• The IBM System/370 family share the

same basic architecture

• This gives code compatibility

— At least backwards

• Organization differs between different

versions

Differences in organization but not architecture

leads to “families”

• Different cost and performance

• Run same code

• Families may span years of technological advancement

Hierarchical Nature of Complex Systems

• Each level of system hierarchy consists of set of components and their

interrelationships

— Operation of components  Function

— Interrelation of components  Structure

• Each successively higher layer describes simplified/more abstract view of lower

levels

Hierarchical Nature of Complex Systems

(continued)

• Breaking system into components or modules

forces designer to develop a detailed

understanding of the data that is passed between them

• Working within the hierarchy, a designer needs

to only concern him/herself with the details of his

or her module at that specific level

• Working with a well-defined set of inputs,

outputs, and function definition, designers can

completely design their module without any

knowledge of how rest of system is made

Modular System Design

Applying a modular methodology to system

design results in:

—a more manageable project

—quicker design time by allowing multiple

people with differing expertise to participate (although up-front investment of time feels like a drawback)

—a higher quality system

—a more maintainable system

—increased module reusability

Modular System Design (continued)

There are two methods to use toward a designing a modular system:

—Top down

—Bottom up

Top Down System Design

• Solving a problem by dividing the system into individual functions and building a

component to satisfy each function

• Benefits of Top Down Design

— Efficient use of components

— Easier to meet performance goals of the

system specification

• Drawbacks of Top Down Design

— More expensive and time consuming

Bottom Up System Design

• Solving a problem using an existing

system (e.g., using DLL's to create a new application)

• Cheaper in small quantities

• Design time is reduced

• Past experiences can be drawn upon

Concept of Black Boxes

• This is the building block of the

hierarchical system design

• If inputs, outputs, and functions are well defined, the designer doesn't need to

know about anything above or below in the system

implementation of circuits and

devices

read/write memory ranging from machine language to high-level languages

(hardware dependent)

contained in read only memory

Structure & Function

• Structure is the way in which components relate to each other

• Function is the operation of individual

components as part of the structure

Data movement to a peripheral

• Data must be passed between computer and I/O devices connected to computer

• Typically to simple devices

• Examples

— monitors and keyboards

— data acquisition

— peripheral control

Data Movement to remote devices (data

• Something needs to monitor operation and maintain control of data processing, data storage, and data movement

• Automated control of computer’s

resources

Functional View

Operations (a) Data movement

Operations (b) Storage

Operation (c) Processing from/to storage

Operation (d)

Processing from storage to I/O

Structure - Top Level

Computer

Main Memory

Input Output

Systems Interconnection Peripherals

Communication

lines

Central Processing Unit

Computer

In-Class Exercise

• Determine which of the previous operations applies each of the following uses:

— Router system

— Hard drive controller

— Video capture or CD player

• Come up with additional examples for each

of the previous operations

Structure - The CPU

and Login Unit

Control Unit

Internal CPU Interconnection

Registers

CPU I/O

Memory

System

Bus

CPU

Structure - The Control Unit

CPU

Control Memory

Control Unit Registers and Decoders

Sequencing Login

Control Unit ALU

Registers

Internal

Bus

Control Unit

In-Class Exercise

• Think back to your first computer

• Try to recall the characteristics

— Processor type

— Processor speed (Hz)

— Memory size

— Characteristics such as:

– Types of storage devices

– Cache

– Bus

– Network

Outline of the Book (1)

• Computer Evolution and Performance

• Computer Interconnection Structures

Outline of the Book (2)

• CPU Structure and Function

• Reduced Instruction Set Computers

• Superscalar Processors

• Control Unit Operation

• Microprogrammed Control

• Multiprocessors and Vector Processing

• Digital Logic (Appendix)

Internet Resources

- Web site for book

• http://WilliamStallings.com/COA/COA7e.html

— links to sites of interest

— links to sites for courses that use the book

— errata list for book

— information on other books by W Stallings

Internet Resources

- Web sites to look for

• WWW Computer Architecture Home Page

• CPU Info Center