CPSC 418 Information

CPSC 418: Information

Go to CpSc 418 home page

Instructor

Mark Greenstreet
Office: CICSR 349
Email: mrg@cs.ubc.ca
Phone: 604-822-3065
Office Hours: W 10:30-12, or by appointment

T.A.

Yang Lu
Office: CICSR 342 (ISD lab)
Email: yanglu@cs.ubc.ca
Phone: 604-822-4487
Office Hours: By appointment

Lectures

Tuesdays & Thursdays 9:30-11:00 AM
Room: CEME 1202

Text Book

The reader for this course is available in the bookstore. The course will consist of reading papers from this collection, with related lectures, homework, exams, etc.
Additional papers may be handed-out during the semester. See the reading list.

Marking

Homework	15%
Papers	15%
Synopses	10%
Midterm (October 22)	25%
Final	35%

A goal of this course is to teach how to read papers about computer architecture. In addition to the readings for the course, there will be two assignments of the form ``find a paper about computer architecture, read it, and write a 2-5 page summary.'' Here are some suggestions of where to find papers. These summaries will be graded for both content and clarity.

As scientists and engineers, you must be able to communicate effectively. Marks will be taken off for poor writing style and grammatical errors that impede understanding. Spell check everything that you type!

First paper due:	October 17, 2002
Second paper due:	November 29, 2002

Synopses

To get the most out of this course, it is essential that you read the papers before class. Lectures will explore, expand upon, and critique the content of the papers. The ability to read is a pre-requisite for this course; I won't spend lecture time reading the papers to you.

I realize that some of you prefer a tangible incentive for preparing for class. In past years, I've had some pop-quizzes. This year, I'm going to try something different. For each paper starting from September 10, I will have four questions:

What is the issue addressed by the paper?
What is the main idea behind the solution (or observations) presented in the paper?
How is this idea substantiated?
Make one observation that goes beyond the paper. For example, you could state why you think the author failed to adequately substantiate his/her/their claims; or you could suggest possible further research; or you could draw connetions between the ideas in the paper and the ideas in other papers you've read in this class.

Your answers should be short. Typically two or three sentences. I reserve the right to take of points for answers longer than fifty words.

Course Outline

This course will build upon the material of CpSc 318 to examine current issues in computer architecture. Traditionally, architecture courses cover topics in the order of instruction sets, memory, and I/O. This means that instruction sets get too much attention and I/O gets neglected. As a remedy, I teach this course in the opposite order.

The first half of the semester will focus on I/O and memory. The survey of I/O emphasis will be on disks and disk arrays. We will also examine networks. The study of caching techniques will begin with a review of caching mechanics, and will focus on caching for large data sets and for shared-memory multiprocessors. These are currently issues for server machines and are likely to become increasingly important for desktop workstations and personal computers in the next few years.

The second half of the semester will focus on architectural support for parallelism. We will first examine super-scalar processors where the processor hardware finds implicit parallelism by analysing the instruction dependencies of the executing program. Super-scalars are the dominant architecture today. We will then compare the super-scalar approach wiht other approaches such as the explicit parallelism of Intel's IA-64 architecture. Following this introduction to instruction level parallelism, we will look at thread level parallelism. For this approach, applications are written as a collection of concurrently executing threads. Executing these threads in parallel can lead to greater performance. I've left the last two lectures open for topics of interest. These include quantum computing, bio-computing, nano-technology, embedded processors, high-speed circuits for pipelines and interconnect, architecture for low power, etc. I will welcome suggestions from the class of topics you would like to see covered.

Information Sources

Read the class newsgroup!

ubc.courses.cpsc.418
should be your primary resource for questions about lectures, assignments, etc. I will read the group often and respond to questions there. Also, if you have information (or the answer) to a question posted, feel free to post a response. I will post corrections or clarifications if needed. I consider constructive participation in in the newgroup to be reasonable grounds for extra-credit -- I can only observer your posting, not your reading.
You are welcome to stop by my office any time, but I may not be there or may be busy. Send email to check if I'm available. The purpose of office hours is to provide you with a time when I guarantee that I will be in my office and CS418 will be my top priority. If there is any reason that I absolutely cannot be available at office hours, I will announce it in class that day and post to the newsgroup. The T.A.s will handle questions regarding homework marks, and will also be available during office hours for technical questions.
All homeworks, handouts, solutions, etc will be installed on the CS418 web pages:

http://www.ugrad.cs.ubc.ca/~cs418/
When something new is installed on the Web, an announcement will be posted to the newsgroup.
Many chip and computer manufacturers now have web pages. A lot of it is fluff, but hard information can sometimes be found. A few sites have already been linked into the course web pages; more will be added.
The newsgroup comp.arch is an excellent source of information on computer architecture. The comp.sys.* hierarchy is for specific machines, such as comp.sys.powerpc.tech for the IBM/Motorola/Apple PowerPC.

Feedback

I strongly encourage you to give me feedback on what you like and don't like about the course, what you find easy or difficult, what homework problems you learned from and which ones you found non-helpful. I also encourage feedback on the papers that I've assigned -- are they too easy, too difficulty, overlap too much with material from CpSc 318, etc.

Cheating

Unattributed use of material from somebody else is plagiarism and constitutes academic misconduct. If in the course of doing your homework or writing a paper of a synopsis, you get material from the web, a book, a research paper, a friend, etc., you must include a citation. Otherwise, your are plagiarizing. In general, good clear citations will improve your score.

For homework, it's ok if you discuss the problems with other students in the class. However, each student must do their solution individually. If you discuss the homework with other members of the class and it is likely that you will work out solutions with similar approaches as a result. State who you worked with in your solution. Be specific -- name the people that you discussed the problem with and the aspects of the solution that you figured out together. As I stated above, I encourage discussions about the concepts. Proper academic conduct requires that you give credit when you receive an idea from someone else.

I basically trust you all not to cheat, and I expect cheating not to be a problem. However, suspected cheating cases will be referred promptly to the University for appropriate disciplinary action.

Acknowledgement

I've adopted much of the material for these pages from Alan Hu's pages from the Spring 1999 instance of this course.