1 / 8

198:211 Computer Architecture

198:211 Computer Architecture. Topics: Administrative Stuff. Christopher Peery Spring 2009. Detail…. Me: Christopher Peery peery@cs.rutgers.edu Office Hour: TBA TAs: Ishani Chakraborty ishantic@cs.rutgers.edu Office Hour: TBA Wei Wang ww@cs.rutgers.edu Office Hour: TBA

pink
Télécharger la présentation

198:211 Computer Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 198:211Computer Architecture • Topics: • Administrative Stuff Christopher Peery Spring 2009

  2. Detail… Me: Christopher Peery peery@cs.rutgers.edu Office Hour: TBA TAs: Ishani Chakraborty ishantic@cs.rutgers.edu Office Hour: TBA Wei Wang ww@cs.rutgers.edu Office Hour: TBA Web: http://www.panic-lab.rutgers.edu/~peery/cs211/ (You’re required to check this page regularly)

  3. More Details… Books: Computer Systems: A Programmer's Perspectiveby Randal E. Bryant and David O'Hallaron The C Programming Language by Brian W. Kernighian & Dennis M. Ritchie Prerequisites: 198:112 What this really means: • You know at least one programming language. • You know something about how to write, run, and test programs. • Elementary knowledge of math and algorithms

  4. Even More Details… Architecture course have been traditionally taught in two way: top-down or bottom-up. We’re going in from the middle. Programmer-Centric Approach. Goals: • Show that by knowing more about the underlying system, one can be more effective as a programmer. • Write programs that are more reliable and efficient. • Understand how programs interact with the underlying hardware. • Learn the ins and outs of a computer’s architecture. • Learn how to do low-level programming.

  5. Yet even more details… What to expect from the course: Will cover key issues and concepts in class. Recitations will provide review and teach you the tools you need. 4-6 Programming Projects (Don’t panic… yet) 1 mid-term and 1 final No homework and no quizzes So what do I expect of you: Come to class Read the book (Listening to me is not good enough) Work through the problems in the book (not really homework… but it helps) Do the projects Ask questions (IMPORTANT)

  6. Outline of Topics Topics: C Programming Information Representation Assembly Language Programming (x86) Digital Logic Processor Architecture Memory Hierarchy Measuring Program Performance Program Linkage

  7. Project Information Projects Sumary: There will be 4-6 projects (not as bad as it sounds). Most projects will require some degree of programming. The high-level programming language of choice is C. No Java. Projects are very “Do-able” if you don’t wait until the last minute to start them. If you do… well that’s your fault. That being said, I will NOT accept any late projects. No excuses. Projects posted on class web-page. Cheating (the sad reality): I know it happens. I don’t like it, I won’t tolerate it, and I will be looking for it . If you get caught, both parties will be punished. So what might be considered cheating?

  8. Last bit of boring details Grading: Mid-term - 25% Final Exam – 35% Projects – 40% Exams are cumulative. No make-up exams except for university sanctioned reasons. Must inform professor before the exam. Don’t assuming informing implies being allowed to take a make-up (see above statement). Make-up will be held the next day, early morning. Projects are not created equally. Later projects are harder and hence worth more.

More Related