MC723 - Computer systems design laboratory

Notices

Objectives

Improve the concepts learned in the Computer Systems Design course through exercises and the modeling of system (s) with processor (s) and peripheral (s). Reinforce programming concepts in large code bases.

Activities

The semester will be divided into two parts: exercises and project. In the exercises section, each student will implement small activities to ensure understanding of some basic topics. In the second part, each group will implement a project that will be defined by the middle of the semester.

All deliveries have an automatic 24-hour grace period, but I will not accept any justification for postponement based on facts that occurred in those 24 hours. The grace period is not valid if you exceed the term limit.

• Exercises (individual, everyone should do)
• Works (in group, 1 work per group)

REFERENCES

• David A. Patterson and John L. Hennessy. Computer Organization Design, The Hardware / Software Interface. Morgan Kaufmann
• Sandro Rigo, Rodolfo Azevedo, Luiz Santos. Electronic System Level Design: An Open-Source Approach Springer, 2011.
• Language ArchC
• Language SystemC

Project Manager

In addition to the time reserved for the course, I can serve students at various alternative times, including parts of the lunch hour and also early evening hours (until 20pm).

To facilitate your service, try to book by email to ensure that I am available on the day. Send a message suggesting an opening time (look at my updated schedule). If you want to show me some code, try to have it installed on the ssh.students.ic.unicamp.br machine so that it is easy to demonstrate on the spot (please avoid bringing something to install on my machine, my experience says that we will have great work to install).

Exercises

Everyone should do each of the following exercises individually:

• 1 Exercise
• 2 Exercise
• 3 Exercise
• 4 Exercise
• 5 Exercise
• 6 Exercise

The exercises should be performed in the classroom. The exercises are completely individual, including the interpretation of the statement. If in doubt, seek exclusively the teacher.

Jobs

See the deadlines on the calendar:

Each delivery must be in the form of a report with a maximum size of 2 pages. All groups must keep the code defined for each delivery for presentation. There will be a draw for the intermediate phases and all groups will make a final presentation directly with the teacher.

What is work

The job is to build a platform with at least 2 processors and 2 new peripherals (you can use all the peripherals made so far, but you will have to create 2 new ones). This platform must run software that must take advantage of the parallelism offered. You are free to choose the program, it should not be any of the programs used in exercise 6. Program suggestions: those chosen in exercise 3, one of the SPLASH-2 benchmark programs, or any other that you can extract parallelism from.

Both peripherals must be created to increase the performance of the platform. Use profilling to find out what to improve on the code, migrate this part of the code to peripherals as per Exercise 4. You do not need to use the caches implemented in Exercise 5.

Your program has to work in parallel. There is no point in running the first part on the first processor while the second is stopped and then running the second part on the second processor while the first is stopped. You will probably need the Lock peripheral, the implementation of barriers, etc. This peripheral does not count as one of the two requested as it must have already been implemented in exercise 4.

Detailed Specification Report

This is the first report where the group must describe, in detail, what will be done in the work. The limit is 2 pages, so just write what you need. I recommend that you follow the following parts:

1. Introduction: Present at a glance what is expected of your platform: features, characteristics, components, motivation to create it, a general diagram of the platform can be useful for future sections, etc.
2. Platform components: Create a subsection for each of the components and indicate relevant questions about each one. Eg communication protocol, software interface, restrictions, form of implementation (at least one goal), etc.
3. Software: What will be done in software, how will it work, what will run on each processor, etc.
4. Address space used by peripherals.
5. Allocation of activities to the components of the group: If the group will divide the activities, indicate which ones will remain with each component.

Delivery format

• Composition of the group and definition of the theme: until 29/05 - 8h. Spreadsheet
• Delivery of the work specification: until 05/06 - 8h. Only one PDF file via susy.
• Presentation of the work specification: 05/06 during class
• Delivery of the final version: until 26/06 - 8am without grace period. Send the package (after make clean and make distclean) and PDF of the report via susy.
• Presentation of the final version: 26/06 during class.

Any delivery out of specification that does not have a prior agreement with the teacher will be strictly disregarded.

Calendar