Systems Programming

Prerequisites

Students are expected to have a solid grasp of simple data structures (such as lists and arrays) and some programming experience. (CSE 116 or equivalent experience.)

Text

There are two texts for this course:

• Computer Systems: A Programmer’s Perspective, Third Edition, by Randal Bryant and David O’Hallaron.

• The C Programming Lanuage, Second Edition, by Brian W. Kernighan and Dennis M. Ritchie.

Both of these books are truly excellent, and we recommend that you consider buying a copy to keep for your career.

Unfortunately CS:APP is quite expensive (more expensive than we would expect, given the number of copies that must be sold per year!). The least expensive legitimate method we am aware of for purchasing this book is RedShelf There is a Second International Edition PDF floating around the Internet that students often pirate; be warned that it has many errors and is different from the required Third Edition text. If you are purchasing a used textbook online, try to make sure you are getting the US Edition, as the International Edition has more errors.

Policies

The ultimate authority for course policies is the course syllabus.

This course additionally adopts Ethan’s general academic integrity policy, which can be found here. His complete list of policies is here.

Topics

The topics to be covered in this course include:

• The C programming language
• Compiler and linker invocation and their roles in program development
• Version control, build, and other systems
• Representation of in-memory data structures
• Memory management
• The kernel/userspace boundary and the system call interface
• Threads
• Synchronization primitives and concurrency

Advice

You can find advice for succeeding in CSE 220 here. This is likely to be one of the more difficult courses you take in your career at UB, both due to the content of the course and to the position it has in the curriculum. We understand this, and are here to support your learning. Work hard, ask questions, and get help when you need it.

Course Structure

This course will be conducted in-person, pending contradictory guidance from SUNY or the University at Buffalo. Students are expected to attend lectures and labs unless they have a University-approved reason to miss. Students must not attend if they are unwell or have reason to believe that they may have contracted COVID-19 or another communicable infection, with or without noticeable symptoms.

The primary deliverables for this course are weekly labs and several larger projects. Labs will consist of short exercises intended to deepen student understanding of course material (and perhaps cover background material for course projects), and will be evaluated in-lab. Course projects will be C language implementations of concepts discussed in class. Projects and labs will make up about half of the final course grade, with the remainder being quizzes and exams.

There is one midterm and one (cumulative) final for this course. These written exams cover theoretical and fundamental materials beyond the specific implementation details required for the programming assignments and labs. A variety of short quizzes will cover lecture content, lab procedures, course policies, and other important material.

There are no graded homeworks for this course. Written homework assignments may be given to help students understand the material, and any material covered in homeworks may appear on exams or quizzes, but such assignments will not be directly evaluated.

Programming Assignments

All projects for this course must be implemented in C and compile and run correctly on the course-provided time-sharing system. Students will be expected to use version control and appropriate build tools (such as make) to manage their projects.