CS 2200 Presentation 1

1
CS 2200Presentation 1
2
Lecturers

• Bill Leahy
• Office CCB 113
• Office Hours
• Mon, Wed, Fri 115 - 215
• and by appointment
• Email bleahy_at_cc.gatech.edu
• AIM ethereal bleahy

3
Course Owner

• Kishore Ramachandran
• Office CCB 220
• Office Hours
• TBA
• and by appointment
• Email rama_at_cc.gatech.edu
• Don't know how available he will be this Summer?

4
Motivation

• How many of you are taking this because youre
  interested in the subject matter?
• How many of you are taking this because it's
  required

5
Old Guy Story
6
Objectives

• Everybody learn a lot about systems
• Have fun!

7
Prerequisites

• ECE 2030 Intro to computer engineering
• CPU datapath
• Instruction-set
• Basic principles of pipelining
• Memory
• Buses
• Networks
• Sequential and combination logic

8
Prerequisites

• CS 2130 Languages and Translation
• C programming
• Translation Process
• Preprocessing
• Compilation
• Linking
• Loading
• Unix
• etc.

9

• OR

10
Prerequisites

• CS2110
• Sequential and combination logic
• Memory
• CPU/Datapath
• Instruction-set
• C programming
• Translation Process
• Preprocessing, Compilation, Linking, Loading
• Unix
• etc.

11
Course Outline

• Broad exposure to computer systems
• Organization of the processor
• Memory hierarchy
• Storage devices
• Parallel processors
• Networking hardware
• Software abstractions in the operating systems
  for orchestrating their usage
• Networking protocols to connect the computer
  system to its environment.

12
Major Topics

• Processor
• Memory hierarchy
• I/O subsystem
• Parallel systems
• Networking.

13
Normal Semester Schedule

• Weeks 1-5
• Processor, Pipelining, Process Abstraction
• Weeks 6-8
• Memory Management, Memory Hierarchy
• Weeks 9-10
• I/O Devices, Device drivers File Systems
• Weeks 11-13
• Parallel Processors, Parallel OS, Threads, etc.
• Weeks 14-16
• Networking Protocols and Distributed Systems

14
Fun Summer Semester Schedule

• Weeks 1-5
• Processor, Pipelining, Process Abstraction
• Weeks 6-7
• Memory Management, Memory Hierarchy
• Weeks 7-8
• Parallel Processors, Parallel OS, Threads, etc.
• Weeks 8-9
• I/O Devices, Device drivers File Systems
• Weeks 9-11
• Networking Protocols and Distributed Systems

15
Details

• Two Quizzes
• Friday, June 9, 2005
• Wednesday, July 7, 2005
• Final date is tentative
• Class Website
• http//www.cc.gatech.edu/classes/AY2006/cs2200_sum
  mer/

16
Teaching Assistants

• Kane Bonnette - Head TA
• David Worsham
• Anne Hewitt

17
Homework/Projects

• Significant homework and project component to go
  with each topic.
• 3 lab hours in the course credit.
• An excellent knowledge of C programming is
  essential for completing the projects

18
HomeworksSubject to Change

• Homework
• 1 No HW1!!!
• 2 Interrupt handler
• 3 Caching exercise
• 4 Thread warmup

• Projects
• 1 LC2200 Datapath/Control
• 2 I/O Interrupt handler
• 3 Virtual memory
• 4 Multi-Threaded Operating System
• 5 Networking

19
A Word About Assignments
20
Grading Scale

• Participation
• Homeworks
• Projects
• Test 1
• Test 2
• Final Exam

• 5
• 10
• 25
• 20
• 20
• 20
• 100

21
PRS

• Personal Response System
• Starts real soon!!!
• Several multiple choice questions per lecture
• Counts 5 of grade
• Purchase units at bookstore (or used)
• Register unit
• http//www.cetl.gatech.edu/prsreg/

22
Newsgroups

• git.cc.class.cs2200.announce (moderated)
• git.cc.class.cs2200

23
WebWork

• Homework Assignments
• Assignment turnin
• Assignment retrieval
• Grades

24
CS 2200 Rules and Regulations

• 1. Academic misconduct is taken very seriously in
  this class. We will analyze what you turn in
  against other students submissions in the current
  semester as well as previous semesters. You are
  required to do your own work without looking at
  other students code no matter what the source is.
  You are also expected and required to report any
  incidents of academic misconduct to the course
  instructor or to the Dean of Students responsible
  for Academic Misconduct. Failure to do so is in
  itself Academic Misconduct.

25
CS 2200 Rules and Regulations

• 2. You are responsible for turning in assignments
  on time. This includes allowing for unforseen
  circumstances. You are also responsible for
  insuring that what you turned in is what you
  meant to turn in. WebWork includes a getback
  feature This allows you to retrieve exactly what
  you submitted and insure that it works. Take
  advantage of this feature.
• 3. In general, programming assignments should be
  turned in with a Makefile and all files needed to
  compile and run the program. The TA grading your
  submission should be able to make and run your
  program without adding files, repairing things
  etc.

26
CS 2200 Rules and Regulations

• 4. Tests and examinations must be taken at the
  scheduled date and time. Please do not ask for
  special treatment because you (or your parents)
  have purchased non-refundable airline tickets.
  The safe time to travel is at the end of or after
  finals week. The finals schedule published at the
  beginning of the semester is TENTATIVE. The
  official schedule gets published very late in the
  semester.

27
CS 2200 Rules and Regulations

• 5. If you need a certain grade in order to stay
  in school, maintain a scholarship, etc. the time
  to worry about this is right from the beginning
  of the course not during the week before finals.
  Grades are based on demonstrated performance not
  individual need based on factors external to the
  course. Please do not request special
  consideration based on this type of situation.
• 6. Final grades will be available from OSCAR
  normally sometime the week after finals. You may
  review your final and discuss your grades during
  the following semester in which you are attending
  Ga Tech. Grades will not be discussed over break.

28
CS 2200 Rules and Regulations

• 7. If you have any personal problems
  (family/illness/etc.) please go to the Dean of
  Student's office located in the Student Services
  Building (Flag Building) next to the Student
  Center. She is equipped and authorized to verify
  the problems and she will issue a note to all
  your instructors making them aware of the problem
  and requesting whatever extension, etc. is
  necessary.

29
CS 2200 Rules and Regulations

• 8. The .announce newsgroup should be read every
  day. Official announcements about course matters
  will be posted there. The general course
  newsgroup is for posting technical questions
  about assignments, tests etc. Complaints,
  questions about your personal problems, etc.
  should be discussed with your instructor in
  person or via email.

30
CS 2200 Rules and Regulations

• 9. Out of consideration to your fellow students
  please turn off cell phones, beepers, wristwatch
  alarms, etc. Also, make every effort to be on
  time for class. If you unavoidably late, please
  sit near the back and try to avoid as much
  disruption to the class as possible.
• 10. If you are graduating and need this course to
  do so please inform your instructor as soon as
  possible.
• 11. Complaints about any aspect of the course
  should be directed to the course instructor
  during office hours or via email.

31
CS 2200 Rules and Regulations

• 12. The deadline for regrades is 2 weeks after an
  assignment grade is posted or returned to you.
  This deadline also applies to picking up items
  which are returned in class. After this deadline
  no grade changes will be made and tests not
  picked up will be destroyed.

32
turku

• You will get access to clusters and to
• turku.cc.gatech.edu
• What does this mean?
• You need a CoC account
• Projects must run on Red Hat 9.0 Linux

33
Getting Your Account

• If you have an active CoC account do nothing!
• Example sk8r.boi_at_cc.gatech.edu
• If you already have a CoC account and it's
  inactive
• You need to go to TSO (CCB 140) and get it
  reactivated
• If you have never had a CoC account request one
  via the web http//www.cc.gatech.edu/cns/forms/ac
  count_form.html

34
LogicWorks

• We will be using LogicWorks this semester for
  Project 1
• LogicWorks is also available on the States
  Cluster machines.
• You will have access to the States Cluster.
  Please don't abuse this privilege.

35
Textbooks

• Logic Works
• PRS Transmitter
• Primary Text available via the Web

36
Questions?
37
Abstraction
Looking at the big picture!
38
Sitrep

• Time The future
• Place The Karaq Wastes
• Action Immediate

39
(No Transcript)
40
(No Transcript)
41
(No Transcript)
42
(No Transcript)
43
(No Transcript)
44
(No Transcript)
45
(No Transcript)
46
Mission Accomplished!

• But how did they do that?

47
Level 0 the Game

• 3D Graphics
• Mouse/Keyboard Control
• Stereo Sound
• Computer players
• Blood
• Guts
• Heroism
• etc.

• Concept
• Storyboards
• Programmers
• Artists
• HCI Experts
• Sound Experts
• Actors
• Animators
• Playtesters

48
Level 1 Application

• Visualization
• Graphics
• UI/HCI
• AI
• Sound
• Game creation
• State machine
• Databases

HLL Programs
49
Level 2 Systems

• Runtime system
• Procedure call/return mechanisms
• Memory allocation
• Middleware
• Middleware is connectivity software that consists
  of a set of enabling services that allow multiple
  processes running on one or more machines to
  interact across a network.

50
Level 3 Operating System

• Resource manager
• Processor(s)
• Memory
• I/O Devices
• etc.

51
Level 4 Compilers

• Bridge between
• High level language
• Runtime
• OS

52
Level 5 Hardware
Register File
ALU
Bus
Physics
53
(No Transcript)
54
Why are we studying this?

• Very cool!
• Need to have working knowledge one level down
• Somebody has to understand how the darn things
  work
• Somebody has to tell CmpEs what we need
• About 40 of the GRE questions!
• Increase appreciation of Circuit City sales force

55
Questions?
56
Assessment
57
(No Transcript)