|Participants and Project Table|
Linaro Performance Challenge
Software Portability and Optimization
Software is sometimes written to work on a specific computer architecture (type of computer), such as on Intel-compatible x86_64 PCs, or IBM Z9 mainframes. This course deals with the challenge of making software compatible with a new architecture in one of two ways:
- Adding additional architecture-specific code so that the software can run on the new architecture ('porting' the software), or
- Removing the architecture-specific code and replacing it with architectural-neutral code, so that it can run on a variety of system architectures (making the software 'portable').
In either case, software can be altered or it can be built in such a way that performance is optimized - so that runs faster, or it uses less memory or other resources. In order to test optimizations, we'll be performing benchmark testing before and after modification.
SPO600 is a professional option in the Seneca School of Information and Communication Technology CTY and CPA programs. First offered: Winter 2014.
SPO600 in Fall 2015
A new computer architecture has appeared: 64-bit ARM systems (also known as "ARM64" or "AArch64"). While AArch64 is showing up in cell phones and tablets, it is also poised to pounce on the datacentre. Most of the work of porting core software to AArch64 has been completed, and at this point, just about everything that runs on x86_64 Linux systems will run an AArch64 systems. However, the x86_64 architecture has been around for many years, and software has been well-optimized to work on that architecture; but AArch64 is new, and it may be possible to get better performance with additional tuning and optimization.
In Fall 2015, the SPO600 course will be focused on optimizing software on AArch64 systems, using the LEAP, Fedora, and CentOS projects as a starting point. We will build, benchmark, and profile specific software subsystems on x86_64 computers, then do the same on AArch64, and identify areas for improvement. Then we'll experiment with compiler options, algorithm changes, and platform-specific code to optimize the performance.
Note that, unlike some other project-based courses, the results of the projects done in SPO600 will be incorporated into the actual "upstream" open source software, and have a real impact on other people. For this reason, projects must be completed in collaboration with the relevant open source communities, using relevant communication tools. Work performed in this course will be licensed using the relevant open source licenses used by the associated community.
Working in an open source community provides the opportunity to build solid real-world experience, your technical skills and reputation, and a network of contacts, all of which are useful in developing your career.
Course Materials / System Requirements
- Course information and labs are online - no textbook is required.
- If available, students in the Fall 2015 SPO600 course may be required to purchase a 64-bit 96Boards computer (such as a HiKey or DragonBoard 410c).
- You must be able to SSH to computer systems at Seneca (CDOT). You can do this using an SSH client program, included with or available for almost all platforms.
- Classes are held in an Active Learning Classroom. You should have a mobile device of some type (laptop, smartphone, tablet) with a wireless network connection (WiFi or mobile) and a video output (VGA or HDMI). If your video output is of a different type (DP/Miracast/MyDP/MiniDP/MiniHDMI/other) you will need an appropriate adapter.
- For productivity, you should have access to a personal Linux installation on a 64-bit (x86_64) computer (see SPO600 Host Setup).
SPO600 is taught by Chris Tyler.
Succeeding in SPO600
There are three keys to success in this course:
1. Work in the open source community. The projects we will be doing are too large and too unfamiliar for you to succeed entirely on your own. You will need to use the community's knowledge, connections, and resources to succeed well. Respect the community's standards, tell the community what you're doing, ask when you have a question, and pull your own weight within the community.
2. Blog. Tell your professor, your colleagues, the community, and everyone else what you're doing. Write a lot and write well, include good technical content, and incorporate links to all relevant resources and the product of your work, and write often. Almost all of your work in this course is submitted by blogging.
3. Be ambitious. In this course, you will need to be the driving force behind your project. The community will help you, but it's up to you to supply the energy. It's best to plan to make a bit of progress each day.
See the Current SPO600 Weekly Schedule for specific dates and topics.
See the online course outline for course details.