(Ebook PDF) The Essentials of Computer Organization and Architecture 4Th
(Ebook PDF) The Essentials of Computer Organization and Architecture 4Th
com
https://ebookluna.com/product/ebook-pdf-the-essentials-of-
computer-organization-and-architecture-4th/
OR CLICK BUTTON
DOWNLOAD NOW
https://ebookluna.com/product/essentials-of-computer-organization-and-
architecture-5th-edition-ebook-pdf/
ebookluna.com
https://ebookluna.com/product/ebook-pdf-essentials-of-computer-
organization-and-architecture-5th-edition/
ebookluna.com
https://ebookluna.com/product/ebook-pdf-computer-organization-
architecture-themes-and-variations/
ebookluna.com
ebookluna.com
Computer Organization And Architecture. Designing For
Performance. 11 Global Edition Edition William Stallings -
eBook PDF
https://ebookluna.com/download/computer-organization-and-architecture-
designing-for-performance-ebook-pdf/
ebookluna.com
https://ebookluna.com/product/ebook-pdf-parallel-computer-
organization-and-design/
ebookluna.com
https://ebookluna.com/product/ebook-pdf-parallel-computer-
organization-and-design-2/
ebookluna.com
https://ebookluna.com/product/ebook-pdf-computer-organization-and-
architecture10th-global-edition/
ebookluna.com
https://ebookluna.com/product/ebook-pdf-computer-organization-and-
design-arm-edition-the-hardware-software-interface/
ebookluna.com
Contents
Preface
CHAPTER 1 Introduction
1.1 Overview
1.2 The Main Components of a Computer
1.3 An Example System: Wading Through the Jargon
1.4 Standards Organizations
1.5 Historical Development
1.5.1 Generation Zero: Mechanical Calculating
Machines (1642–1945)
1.5.2 The First Generation: Vacuum Tube
Computers (1945–1953)
1.5.3 The Second Generation: Transistorized
Computers (1954–1965)
1.5.4 The Third Generation: Integrated Circuit
Computers (1965–1980)
1.5.5 The Fourth Generation: VLSI Computers
(1980–????)
1.5.6 Moore’s Law
1.6 The Computer Level Hierarchy
1.7 Cloud Computing: Computing as a Service
1.8 The Von Neumann Model
1.9 Non–Von Neumann Models
1.10 Parallel Processors and Parallel Computing
1.11 Parallelism: Enabler of Machine Intelligence—
Deep Blue and Watson
Chapter Summary
Further Reading
References
Review of Essential Terms and Concepts
Exercises
CHAPTER 6 Memory
6.1 Introduction
6.2 Types of Memory
6.3 The Memory Hierarchy
6.3.1 Locality of Reference
6.4 Cache Memory
6.4.1 Cache Mapping Schemes
6.4.2 Replacement Policies
6.4.3 Effective Access Time and Hit Ratio
6.4.4 When Does Caching Break Down?
6.4.5 Cache Write Policies
6.4.6 Instruction and Data Caches
6.4.7 Levels of Cache
6.5 Virtual Memory
6.5.1 Paging
6.5.2 Effective Access Time Using Paging
6.5.3 Putting It All Together: Using Cache, TLBs,
and Paging
6.5.4 Advantages and Disadvantages of Paging and
Virtual Memory
6.5.5 Segmentation
6.5.6 Paging Combined with Segmentation
6.6 A Real-World Example of Memory Management
Chapter Summary
Further Reading
References
Review of Essential Terms and Concepts
Exercises
Glossary
Answers and Hints for Selected Exercises
Index
Preface
TO THE STUDENT
This is a book about computer organization and architecture. It focuses on
the function and design of the various components necessary to process
information digitally. We present computing systems as a series of layers,
starting with low-level hardware and progressing to higher-level software,
including assemblers and operating systems. These levels constitute a
hierarchy of virtual machines. The study of computer organization focuses on
this hierarchy and the issues involved with how we partition the levels and
how each level is implemented. The study of computer architecture focuses
on the interface between hardware and software, and emphasizes the structure
and behavior of the system. The majority of information contained in this
textbook is devoted to computer hardware, computer organization and
architecture, and their relationship to software performance.
Students invariably ask, “Why, if I am a computer science major, must I
learn about computer hardware? Isn’t that for computer engineers? Why do I
care what the inside of a computer looks like?” As computer users, we
probably do not have to worry about this any more than we need to know
what our cars look like under the hood in order to drive them. We can
certainly write high-level language programs without understanding how
these programs execute; we can use various application packages without
understanding how they really work. But what happens when the program we
have written needs to be faster and more efficient, or the application we are
using doesn’t do precisely what we want? As computer scientists, we need a
basic understanding of the computer system itself in order to rectify these
problems.
There is a fundamental relationship between the computer hardware and
the many aspects of programming and software components in computer
systems. In order to write good software, it is very important to understand
the computer system as a whole. Understanding hardware can help you
explain the mysterious errors that sometimes creep into your programs, such
as the infamous segmentation fault or bus error. The level of knowledge
about computer organization and computer architecture that a high-level
programmer must have depends on the task the high-level programmer is
attempting to complete.
For example, to write compilers, you must understand the particular
hardware to which you are compiling. Some of the ideas used in hardware
(such as pipelining) can be adapted to compilation techniques, thus making
the compiler faster and more efficient. To model large, complex, real-world
systems, you must understand how floating-point arithmetic should, and
does, work (which are not necessarily the same thing). To write device
drivers for video, disks, or other I/O devices, you need a good understanding
of I/O interfacing and computer architecture in general. If you want to work
on embedded systems, which are usually very resource constrained, you must
understand all of the time, space, and price trade-offs. To do research on, and
make recommendations for, hardware systems, networks, or specific
algorithms, you must acquire an understanding of benchmarking and then
learn how to present performance results adequately. Before buying
hardware, you need to understand benchmarking and all the ways that others
can manipulate the performance results to “prove” that one system is better
than another. Regardless of our particular area of expertise, as computer
scientists, it is imperative that we understand how hardware interacts with
software.
You may also be wondering why a book with the word essentials in its
title is so large. The reason is twofold. First, the subject of computer
organization is expansive and it grows by the day. Second, there is little
agreement as to which topics from within this burgeoning sea of information
are truly essential and which are just helpful to know. In writing this book,
one goal was to provide a concise text compliant with the computer
architecture curriculum guidelines jointly published by the Association for
Computing Machinery (ACM) and the Institute of Electrical and Electronic
Engineers (IEEE). These guidelines encompass the subject matter that experts
agree constitutes the “essential” core body of knowledge relevant to the
subject of computer organization and architecture.
We have augmented the ACM/IEEE recommendations with subject
matter that we feel is useful—if not essential—to your continuing computer
science studies and to your professional advancement. The topics that we feel
will help you in your continuing computer science studies include operating
systems, compilers, database management, and data communications. Other
subjects are included because they will help you understand how actual
systems work in real life.
We hope that you find reading this book an enjoyable experience, and
that you take time to delve deeper into some of the material that we have
presented. It is our intention that this book will serve as a useful reference
long after your formal course is complete. Although we give you a substantial
amount of information, it is only a foundation upon which you can build
throughout the remainder of your studies and your career. Successful
computer professionals continually add to their knowledge about how
computers work. Welcome to the start of your journey.
TO THE INSTRUCTOR
This book is the outgrowth of two computer science organization and
architecture classes taught at Penn State Harrisburg. As the computer science
curriculum evolved, we found it necessary not only to modify the material
taught in the courses, but also to condense the courses from a two-semester
sequence into a three-credit, one-semester course. Many other schools have
also recognized the need to compress material in order to make room for
emerging topics. This new course, as well as this textbook, is primarily for
computer science majors and is intended to address the topics in computer
organization and architecture with which computer science majors must be
familiar. This book not only integrates the underlying principles in these
areas, but it also introduces and motivates the topics, providing the breadth
necessary for majors while providing the depth necessary for continuing
studies in computer science.
Our primary objective in writing this book was to change the way
computer organization and architecture are typically taught. A computer
Random documents with unrelated
content Scribd suggests to you:
promotion, 4;
leaves for Mexico, 7;
at Camargo and Matamoros, 10-14, 23-24;
march to Victoria, 24-43;
at Victoria, 43-46;
march to Tampico, 46-50;
at Lobos, 51;
at Vera Cruz, 53-73;
march to Cerro Gordo, 74-79;
battle of Cerro Gordo, 80-90;
march to Jalapa, 90-93;
at Mexico City, 92-93.
Marquesoto, 40.
Padilla, 42.
Patterson, Gen. Robert, 14, 15, 16, 20-21, 22 (note), 23-24, 26, 27,
30, 31-32, 33, 35, 37, 40, 41, 43, 56.
Pillow, Gen. Gideon J., 15, 23, 25, 26, 35, 37, 52 (note), 79, 81-87.
Plan del Rio, 78-79.
Reilly, 89.
Santander, 37.
Smith, Lieut. Gustavus W., 2, 4, 7, 11, 20-21, 23, 25, 26, 31, 36, 38,
55, 57, 58, 59, 60-62, 63, 68, 74, 75, 78, 80, 93.
Tamaulipas, 51.
Tampico, 50-51.
Twiggs, Gen. David E., 47, 48, 52, 56, 74, 79, 80, 82, 87-90.
Victoria, 43-46.
Updated editions will replace the previous one—the old editions will
be renamed.
1.D. The copyright laws of the place where you are located also
govern what you can do with this work. Copyright laws in most
countries are in a constant state of change. If you are outside the
United States, check the laws of your country in addition to the terms
of this agreement before downloading, copying, displaying,
performing, distributing or creating derivative works based on this
work or any other Project Gutenberg™ work. The Foundation makes
no representations concerning the copyright status of any work in
any country other than the United States.
Our website is not just a platform for buying books, but a bridge
connecting readers to the timeless values of culture and wisdom. With
an elegant, user-friendly interface and an intelligent search system,
we are committed to providing a quick and convenient shopping
experience. Additionally, our special promotions and home delivery
services ensure that you save time and fully enjoy the joy of reading.
ebookluna.com