Computer Architecture--The Essentials -- Article Index + Overview

Contents:

Overview (below)

1. Introduction and Overview
Part I: Basics of Digital Logic and Data Representation -- The Fundamentals from Which Computers are Built
2. Fundamentals of Digital Logic
3. Data and Program Representation
Part II: Processors: The Engines that Drive Computation
4. The Variety of Processors and Computational Engines
5. Processor Types and Instruction Sets
6. Data Paths and Instruction Execution
7. Operand Addressing and Instruction Representation
8. CPUs: Microcode, Protection, and Processor Modes
9. Assembly Languages and Programming Paradigm
Part III: Memories: Program & Data Storage Technologies
10. Memory and Storage
11. Physical Memory and Physical Addressing
12. Caches and Caching
13. Virtual Memory Technologies and Virtual Addressing
Part IV: Input and Output: External Connections and Data Movement
14. Input /Output Concepts and Terminology
15. Buses and Bus Architectures
16. Programmed and Interrupt Driven I/O
17. A Programmer's View of Devices, I/O, and Buffering
18. Parallelism
19. Data Pipelining
20. Power and Energy
21. Assessing Performance
22. Architecture Examples and Hierarchy
23. Hardware Modularity

Lab Exercises for a Computer Architecture Course

ARM Register Definitions and Calling Sequence

Overview

Hardware engineering has shifted the use of discrete electronic components to the use of programmable devices. Consequently, programming has become much more important. Programmers who understand how hardware operates and a few basic hardware principles can construct software systems that are more efficient and less prone to errors. Consequently, a basic knowledge of computer architecture allows programmers to appreciate how software maps onto hardware and to make better software design choices. A knowledge of the underlying hardware is also a valuable aid in debugging because it helps programmers pinpoint the source of problems quickly.

The text is suitable for a one-semester undergraduate course. In many Computer Science programs, a course on computer architecture or computer organization is the only place in the curriculum where students are exposed to fundamental concepts that explain the structure of the computers they program. Unfortunately, most texts on computer architecture are written by hardware engineers and are aimed at students who are learning how to design hardware. This text takes a different approach: instead of focusing on hardware design and engineering details, it focuses on programmers by explaining the essential aspects of hardware that a programmer needs to know. Thus, topics are explained from a programmer's point of view, and the text emphasizes consequences for programmers.

This guide is divided into five parts. Part I covers the basics of digital logic, gates, data paths, and data representation. Most students enjoy the brief look at the underlying hardware (especially because the text and labs avoid minute hardware details). Parts II, III, and IV cover the three primary aspects of architecture: processors, memories, and I/O systems. In each case, the sections give students enough background to understand how the mechanisms operate and the consequences for programmers without going into many details. Finally, Part V covers the advanced topics of parallelism, pipelining, power and energy, and performance.

Appendix 1 describes an important aspect of the course: a hands-on lab where students can learn by doing. Although most lab problems focus on programming, students should spend the first few weeks in lab wiring a few gates on a breadboard. The equipment is inexpensive (we spent less than fifteen dollars per student on permanent equipment; students purchase their own set of chips for under twenty dollars).

Appendix 2 provides a quick introduction to x86 assembly language and the x64 extensions. Many professors teach x86 and have requested that it be included. The material is in an appendix, which means that professors who choose to focus on a RISC assembly language (e.g., the ARM architecture) can use it for comparison.

NEXT

Related Articles -- Top of Page -- Home