|<div style="background:#ffff00">[[Current SPO600 Weekly Schedule|Weekly Schedule]]</div>[[Fall 2015 Current SPO600 Participants|Participants and Project Table]]<br />[[Fall 2015 SPO600 Course Project|Course Project]https://telescope.cdot.systems Telescope]<br />[httphttps://wwwict.senecacollege.ca/ssos/findWithoutSemestercourse/spo600/sict Course Outline]<br />[[media:SPO600 Course PoliciesWinter 2022 addendum.pdf|Course PoliciesWinter 2022 Addendum]]<br />[http://linaro.org Linaro]<br />[http://performance.linaro.org Linaro Performance ChallengeSPO600 Course Policies|Course Policies]<br />[http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT]<br />

 <!-- {{Admon/tip|Thinking of taking this course in Winter 2016?|[[SPO600 - Information for Prospective Students|Here is some information for prospective students.]]}}-->

== SPO600 in Winter 2016 2022 ==

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 relatively new, and it may be possible to get better performance with additional tuning and optimization.

In Winter 2016this semester, the SPO600 course will be focused on optimizing software on AArch64 systems, using and specifically on building infrastructure to make it easier to use indirect functions (similar to the [http://leapprojectglibc "ifunc" capability) for runtime implementation selection.ca LEAP]This technique is widely used in a few places -- such as in glibc, [http://fedoraprojectthe GNU standard C library -- but it would be great if we could easily use it in other places.org Fedora]This would allow (for example) two versions of a particular function to be automatically compiled, with and [http:without support for particular hardware features (such as Scalable Vector Extensions (SVE//centos.org CentOS] projects as a starting point. We will be benchmarking SVE2)), and for the performance of open source software stacks on AArch64 relative best version to the raw performance of the hardware and searching for optimization opportunitiesbe 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 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 [[SPO600 Communication Tools|communication tools]]. Work performed in this course will be licensed using the relevant open source licenses used by the associated community.

<!-- '''Strongly 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 (VGA or HDMI). If your video output is of a different type (VGA/DVI/DP/Miracast/MyDP/MiniDP/MiniHDMI/other) you will need an appropriate adapter.

* '''If available''', students Students in the SPO600 course may want to purchase a 64-bit [https://www.96boards.org/ 96Boards] ARM computer (, such as a Rasbperry Pi 4 or Raspberry Pi 400 -- but you will need to run a 64-bit operating system, such as [https://www.96boardsfedoraproject.org/productswiki/hikeyArchitectures/ HiKey] or [https:ARM//www.96boards.org/products/dragonboard410c/ DragonBoard 410cRaspberry_Pi Fedora AArch64]).-->

1. '''Work ''in'' the open source communityBlog.''' The projects we will be doing are too large and too unfamiliar for you to succeed entirely on Tell your own. You will need to use the community's knowledgeprofessor, connectionsyour colleagues, and resources to succeed well. Respect the community's standards, tell the community and everyone else what you're doing. <u>Write a lot</u> and write well, ask when you have a questioninclude good technical content, and incorporate links to all relevant resources and the product of your work, and pull write often. Almost all of your own weight within the communitywork in this course is submitted by blogging.

2. '''BlogBe ambitious.''' Tell your professorIn this course, you will need to be the driving force behind your colleagues, the project. The communitywill help you, and everyone else what but it's up to you're doing. <u>Write a lot</u> and write well, include good technical content, and incorporate links to all relevant resources and supply the product of your work, and write often. Almost all of your work in this course is submitted by bloggingenergy.

3. '''Be ambitiousWork ''in'' the open source community.''' In this course, The projects we will be doing are too large and too unfamiliar for you to succeed entirely on your own. You will need to be use the driving force behind your projectcommunity's knowledge, connections, and resources to succeed well. The Respect the community's standards, tell the community will help what you're doing, but it's up to ask when you to supply have a question, and pull your own weight within the energycommunity.

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.