Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
These are the Lecture Slides of Computer Systems which includes Writing to Cache, Memory Access, Simple Direct-Mapped Cache, Inconsistent Memory, Write-Through Caches, Write-Back Caches, Finishing Write Back, Write Misses etc.Key important points are: Software Interface, Hardware Interface, Operating Systems, Course Mechanics, Academic Integrity, Architecture and Organization, Instruction Set Architectures, Computer Architecture, Architecture Families
Typology: Slides
1 / 13
The hardware / software interface– the elements of a computer system– what parts are visible to the software– instruction set architecture (ISA)– what happens inside the CPUO
-^
Operating systems– services an OS performs for an application
design of various OS components
6
3 Lectures/week
-^
Homeworks most weeks– Written problems, small programming exercises
-^
Office hours tba, scattered through week– Use them!O
-^
Online discussion board to stay in touch betweenclasses / office hours
7
6-7 assignments (50%)
g^
Midterm, tentatively Fri. April 30 or Mon. May 3 (20%)
-^
Final, Tue. June 8, 2:30 (25%)
-^
Participation, citizenship, etc. (5%)
Late policy: 4 “late days”, at most 2 on any singleassignment, counted in 24 hour chunks, otherwise nolate assignments.
g
8
Policy on the course web.
Read it!
y
Do your own work – always explain anyunconventional action on your part
-^
I trust you completely
-^
I have no sympathy for trust violations – nor shouldyouyou
-^
Honest work is the most important feature of auniversity. It shows respect for your colleagues andyourself.
9
For our purposes (for now)…
p^
p^
i mainmemory
processor
processor/memory bus
I/O bI/O bus
networkinterface
harddisk
video /camera
opticaldrive
serialports
10
interface
disk
camera
drive
ports
-^
Architecture (the boxes)
(^
)
registers addressing
programmer’s view of the
registers, addressing – programmer s view of thehardware
-^
Organization / Implementation (inside the boxes)– components and connections– how instructions are implemented in hardware
many different organizations can implement a single
architecture
11
Software
ISA
Hardware
ISA
Interface between hardware and software– abstraction: hide HW complexity from the software
through a set of simple operations and devices add,
mul,
and,
lw,
...
12
Specification of how to program a specific computer
p
p^
g^
p^
p
family– what instructions are available?– how are the instructions formatted into bits?– how many registers and what is their function?
how is memory addressed?
13
IBM 360, 370, … (the first computer family)
p
y)
PowerPC 601, 603, …
-^
Intel x86: 286, 386, 486, Pentium, P4, Core…
-^
Intel IA64 Itanium
SUN Sparc
-^
ARM family
-^
ARM family
14
In this class, we’ll use the MIPS instruction set architecture (ISA) to illustrate
t^
i^
bl^
l^
d^
hi^
i^
ti
concepts in assembly language and machine organization^ —
Of course, the concepts are not MIPS-specific — MIPS is just convenient because it is real, yet simple (unlike x86)
-^
The MIPS ISA is still used in many places today Primarily in embeddedThe MIPS ISA is still used in many places today. Primarily in embeddedsystems, like:^ —
Various routers from Cisco — Game machines like the Nintendo 64 and Sony Playstation 2
15
To start: learn to program at the architecture /
p
g
instruction set / memory level– Information representation (bits, bytes, …)– MIPS assembly language programming
-^
Then look at some of the core implementation issues
Pipelining
Hardware from the programmer’s perspective:Hardware from the programmer s perspective:– How does my code run?– Why is it fast or slow?
y
16
-^
Remember the big picture– What are we trying to accomplish, and why?
-^
Read the textbooks– They’re clear well-organized and well-written
They re clear, well organized, and well written(particularly P&H). Work through the examples and trysome exercises on your own. Read the “Real Stuff”and “Historical Perspective” sections.
p
-^
Talk to each other– You can learn a lot from other students, both by asking
and answering questionsand answering questions.
-^
Help us help you– Come to lectures and office hours. Use the discussion
board Ask lots of questions! Check out the web pagesboard. Ask lots of questions! Check out the web pages.
17