Changes

{{Chris Tyler Draft}}<!-- {| style="float: right; margin: 0 0 3em 2em; border: 1px solid black;"

|<div style="background:#ffff00">[[Fall 2013 SBR600 Current SPO600 Weekly Schedule|Weekly Schedule]]</div>[[Fall 2013 SBR600 Current SPO600 Participants|Participants and Project Table]]<br />[[SBR600 Potential Projects|Potential Project List]]<br https://>[[Fall 2013 SBR600 Presentation Schedule|Release Presentation Schedule]telescope.cdot.systems Telescope]<br />[https://scs.senecacict.onsenecacollege.ca/course/sbr600 spo600 Course Outline]<br />[[Fedora ARM Secondary Architecturemedia:SPO600 Winter 2022 addendum.pdf|Winter 2022 Addendum]]<br />[http://pidora.ca Pidora[SPO600 Course Policies|Course Policies]]<br />|}[http[Category://fedoraproject.org Fedora ProjectSPO600]<br />[http://docs.fedoraproject.org/ Fedora documentation]<br !-- {{Admon/>tip|Thinking of taking this course?|[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]<br />[http://kojiSPO600 - Information for Prospective Students|Here is some information for prospective students.fedoraproject.org Fedora Koji]<br />[http://koji.pidora.ca Pidora Koji]|}}-->[[Category:SPO600]]= Software Portability and Optimization =

= Software Porting 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 Z-series mainframes. This course is about bringing software to a new architecture. This course deals with the challenge of making software compatible with a new architecture in one of two ways:

# 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').

This course SPO600 is a professional option in the [http://ict.senecac.on.ca/ Seneca School of Information and Communication Technology] [https://ict.senecacollege.ca/academic-programs/cty/overview CTY] and [https://ict.senecacollege.ca/academic-programs/cpa/overview CPA] programs. First offered: Winter 2014. == SPO600 in Winter 2022 ==

== SPO600 A new computer architecture has appeared: 64-bit ARM systems (also known as "ARM64" or "AArch64"). While AArch64 is showing up in Winter 2014 ==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 relatively new, and it may be possible to get better performance with additional tuning and optimization.

In this semester, the SPO600, you'll course will be working directly with open source communities to port focused on optimizing software. This semesteron AArch64 systems, we'll be collaborating with a project set up by Jon "Maddog" Hall and [http://linaro.org Linaro] specifically on building infrastructure to make it easier to port and optimize software which doesn't currently run on 64-bit ARM use indirect functions (aarch64similar to the glibc "ifunc" capability) computersfor runtime implementation selection. This project has identified around 1400 software packages that need worktechnique is widely used in a few places -- such as in glibc, the GNU standard C library -- but it would be great if we could easily use it in other places. This would allow (As for example) two versions of a bonusparticular function to be automatically compiled, completed projects may be eligible with and without support for recognition particular hardware features (such as Scalable Vector Extensions (SVE/SVE2)), and possibly prizes from Linaro)for the best version to be automatically used at runtime.

Note that, unlike some other project-based courses, the results of the projects done in SPO600 will eventually be incorporated into the actual "upstream" open source projectssoftware, 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 [[SPO600 Communication Tools|communication tools]]. Work performed in this course will be licensed using the relevant open source licenses used by the associated community.

* Course information and labs are online- no textbook is required. '''Required:'''* You '''must''' be able to [[SSH]] to [[SPO600 Servers|computer systems]] at Seneca (CDOT). You can do this using an SSH client program, included with or available for almost all platforms.* You '''must''' be able to participate in synchronous (live) streaming classes and be able to view/stream video content. <!-- '''Recommended:'''* 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 (HDMI). If your video output is of a different type (VGA/DVI/DP/Miracast/MyDP/MiniDP/MiniHDMI/other) you will require need an appropriate adapter.* For productivity, you '''should''' have access to a personal Linux installation on a 64-bit (x86_64) computer (ideally, a fast onesee [[SPO600 Host Setup]]). This * Students in the SPO600 course may be on your own laptop, on want to purchase a large/fast virtual machine on your laptop64-bit ARM computer, on an SSH-accessible system (such as a home desktop computer), Rasbperry Pi 4 or on a SATA disk pack or USB drive for use with the Seneca computers.* You Raspberry Pi 400 -- but you will need to be able to ssh to computer systems at Seneca (CDOT)run a 64-bit operating system, such as [https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi Fedora AArch64].-->

1. '''Blog.''' Tell your professor, your colleagues, the community, and everyone else what you're doing. <u>Write a lot</u> 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. 2. '''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. 3. '''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.

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 [[Winter 2013 Current SPO600 Weekly Schedule]] for specific dates and topics.

See the online [https://ict.senecacollege.ca/course/spo600 course outline] for course details, and the [[media:SPO600 Winter 2022 addendum.pdf|Winter 2022 Addendum]] for additional course details.