1,885
edits
Changes
→Evaluation
[[Category:Winter 2018 SPO600]]
This is the schedule and main index page for the [[SPO600]] ''Software Portability and Optimization'' course for Winter 2018.
== Schedule Summary Table ==
{|cellspacing="0" width="100%" cellpadding="5" border="1" style="background: #e0e0ff"
|-
|-
|21||Sep 11Jan 15||[[#Week 2 1 - Class I|Computer Architecture Overview - Binary representation, processor internals, instruction set architectureIntroduction]]||[[#Week 2 1 - Class II|Compiled C Lab Account setup for this course. / How is code accepted into an open source project? (Lab 2)]]<!-- Overview of Working with Code and Building Software - Toolchains, compiler stages, switches and flags, binary file contents (Lab 21)]] -->||[[#Week 2 1 Deliverables|Blog your conclusion to Labs 1 and 2Set up accounts.]]
|-
|32||Sep 18Jan 22||[[#Week 3 2 - Class I|Assembly Lab (Lab 3)Computer Architecture Overview - Binary representation, processor internals, instruction set architecture]]||[[#Week 3 2 - Class II|Assembly Lab (Lab 3 - continued) and Code Bulding Compiled C Lab (Lab 42)]]||[[#Week 3 2 Deliverables|Blog your results conclusion to Labs 1 and conclusions for Lab 32.]]
|-
|-style="background: #f0f0ff"3|4|Jan 29|Sep 25||colspan="[[#Week 3" align="center"- Class I|Linaro Connect Assembly Lab (No ClassesLab 3) - Complete the ]]||[[#Week 43 - Class II|<strike>Assembly Lab (Lab 3 - continued) and Code Building Bulding Lab]] (Lab 4) in preparation </strike>]] <span style="color: #ff0000"><b>Class cancelled</b></span>||[[#Week 3 Deliverables|Blog your results and conclusions for your ProjectLab 3]]
|-
|5-|4|Oct 2|Feb 5||[[#Week 5 4 - Class I|Compiler OptimizationsAssembly Lab (Lab 3) Continued...]]||[[#Week 5 4 - Class II|SIMD and Auto-Vectorization Assembly Lab (Lab 53)Continued...]]||[[#Week 5 4 Deliverables|Blog your Auto-Vectorization Lab (Lab 5) 3 results.]]
|-
|65||Oct 9Feb 12||style="background: [[#f0fff0"Week 5 - Class I|(Thanksgiving - No class)Compiler Optimizations]]||[[#Week 6 5 - Class II|SIMD and Auto-Vectorization (Lab 4 as Homework); Algorithm Selection (Lab 65)]]||[[#Week 6 5 Deliverables|Blog about your the conclusion to Lab 4 and Lab 5.]]|-<!--Auto-vectorization (Lab 5)Algorithm Selection (Lab 6)Inline Assembler (Lab 7)-->|6||Feb 19||[[#Week 6 - Class I|Inline Assembler (Lab 6).]]||[[#Week 6 - Class II|Project: Selecting, Building, Benchmarking, and Profiling]]||[[#Week 6 Deliverables|Blog your conclusion to Lab 6 and blog about your project]]
|-
|-||Feb 26||style="background: #ffd0d0f0f0ff"|colspan="5" align="center"|StrikeReading Week
|-
|x77||Nov 20Mar 5||style="background: [[#ffd0d0"Week 7 - Class I|StrikeProject Discussion]]||style="background: [[#f0f0ff"Week 7 - Class II|Profiling]]|(NSERC IRCC Meetings - No class)|[[#Week 7 Deliverables| Blog about your project.]]
|-
|x88||Nov 27Mar 12||[[#Week x8 8 - Class I|Course Review & Revised PlansSysadmin for Programmers, Project Discussion]]||[[#Week x8 8 - Class II|Inline Assembler (Lab 7)Memory]]||[[#Week x8 8 Deliverables|Blog about your results for Lab 7project.]]
|-
|x99||Dec 4Mar 19||[[#Week x9 9 - Class I|Project: Memory (continued), Building, Benchmarking, and Profilingtesting software]]||[[#Week x99 - Class II|Project HackingAtomics]]||[[#Week x9 9 Deliverables|Blog about your project.]]
|-
|x1010||Dec 11Mar 26||[[#Week x10 10 - Class I|Project Hacking]]||[[style="background: #Week x10 - Class IIf0f0ff" align="center|Project Hacking - End of Stage I]]Good Friday (Holiday)||[[#Week x10 10 Deliverables|Blog about your project, including Stage I report.]]
|-
|x1111||Dec 18Apr 2||[[#Week x11 11 - Class I|Project Hacking]]||[[#Week 11 - Class II|Project HackingCompiler Intrinsics]]||[[#Week X11 11 Deliverables|Blog about your project.]]
|-
|x1212||Jan 1Apr 9||[[#Week 12 - Class I|<strike>Project Hacking</strike> <span style="backgroundcolor: #f0fff0ff0000"|(New Year's Day - No class)><b>Class cancelled</b></span>]]||[[#Week x12 12 - Class II|Project Hacking]]||[[#Week x12 12 Deliverables|Blog about your project.]]
|-
|x1313||Jan 8Apr 16||[[#Week x13 13 - Class I|Wrap-Up Discussion; end of project Stage II.Project Hacking]]||style="background: [[#f0f0ff"Week 13 - Class II|(Course finished)Wrap-up Discussion]]||[[#Week x13 13 Deliverables|Blog about your project, including the final/Stage II report, and write a wrap-up post about the course.]]
|-
!Category!!Percentage!!Evaluation Dates
|-
|Communication||align="right"|20%||January (blog posts up to Feb 4, 5%), End of September February (March 4, 5%), End of November March (Dec 3 - 7.April 2, 5%), end of course (Jan 8 - 7.April 22, 5%).
|-
|Quizzes||align="right"|10%||May be held during any class, usually at the start of class. A minimum of 5 one-page quizzes will be given. No make-up/retake option is offered if you miss a quiz. Lowest 3 scores will not be counted.
|-
|Labs||align="right"|10%||See deliverables column above. All labs must be submitted by Jan 8April 21, but it is best if you stay on top of the labs and submit according to the table above.
|-
|Project work||align="right"|60%||2 3 stages: 15% (March 18), 20% (Dec 14April 10) / 40, 25% (Jan 8April 22).
|}
== Week 1 ==
==== Introduction to the Problems ====
==== General Course Information ====
* Course resources are linked from the CDOT wiki, starting at http://wiki Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in. Click here if you have trouble logging in..cdot.senecacollege.ca/wiki/index.php/SPO600 (Quick find: This page will usually be Google's top result for a search on "SPO600").
* Coursework is submitted by blogging.
* Quizzes will be short (1 page) and will be held without announcement at any time, generally at the start of class. Your lowest three quiz scores will not be counted, so do not worry if you miss one or two.
* All classes will be held in an [[Active Learning Classroom]] -- you are encouraged to bring your own laptop to class. If you do not have a laptop, consider signing one out of the Learning Commons for class, or using a smartphone with an HDMI adapter.
* For more course information, refer to the SPO600 Weekly Schedule (this page), the [http://www.senecacollege.ca/ssos/findWithoutSemester/spo600/sict Course Outline], and [[SPO600 Course Policies]].
==== Discussion of how open source communities work ====
# Course setup:
## Set up your [[SPO600 Communication Tools]] - in particular, set up a blog and add it to [http://zenit.senecac.on.ca/~chris.tyler/planet/ Planet CDOT] (via the [[Planet CDOT Feed List]]).
## Add yourself to the [[Fall 2017 Winter 2018 SPO600 Participants]] page (leave the projects columns blank).## Generate a [[SPO600_Servers#Preparatory_Steps|pair of keys]] for [[SSH]] and email the public key to your professor, so that he can set up your access to the [[SPO600_Servers SPO600 Servers|class servers]].
## Sign and return the [[Open Source Professional Option Student Agreement]] (this will be done on paper in class).
# Optional (recommended): [[SPO600 Host Setup|Set up a personal Fedora system]].
# Optional: Purchase an AArch64 development board (such as a [http://96boards.org 96Boards] HiKey or Raspberry Pi 2/3. If you use a Pi, install a 64-bit Linux operating system on it, not a 32-bit version).
== Week 2 ==
=== Week 2 - Class I ===
==== Reference ====
* [[Computer Architecture]] and [[:Category:Computer Architecture|Computer Architecture Category]]
* [[Aarch64 Register and Instruction Quick_StartQuick Start]]* [[x86_64 Register and Instruction Quick_StartQuick Start]]
=== Week 2 - Class II ===
=== Week 2 Deliverables ===
=== Week 3 - Class I ===
* [[Assembler Basics]]
* [[Syscalls]]
* [[SPO600 Assembler Lab|Assembler Lab (Lab 3)]].
=== Week 3 - Class II ===
* <strike>Complete Lab 3.* [[SPO600 Code Building Lab|Code Building Lab (Lab 4)]]</strike> <span style="color: #ff0000">Class cancelled</span>
=== Week 3 Deliverables ===
* Complete and blog Blog your results, conclusions, and reflections initial experience on the [[SPO600 Assembler Lab|Assembler Lab (Lab 3)]].
== Week 4 ==
=== Week 4 - Class I === * Complete and blog your results, conclusions, and reflections Continue work in class on the [[SPO600 Code Building Assembler Lab|Code Building Assembler Lab (Lab 3)]]. === Week 4- Class II === * Continue work in class on the [[SPO600 Assembler Lab|Assembler Lab (Lab 3)]]. === Week 4 Deliverables === * Blog your [[Lab 3]] results.
== Week 5 ==
* [[Compiler Optimizations]]
=== Week 5 - Class II ===
* Advanced Compiler Optimizations
** [[Profile Guided Optimization]]
** [[Link Time Optimization]]
* Introduction to Vector Processing/SIMD
** [[SPO600 Vectorization Lab|Vectorization Lab]] (Lab 4) as homework* [[SPO600 Algorithm Selection Lab|Algorithm Selection Lab]] (Lab 5)in work groups
=== Week 5 Deliverables ===
* Blog your results for the [[SPO600 Vectorization Lab|Vectorization Lab4]] (and [[SPO600 Algorithm Selection Lab|Lab 5) ]] -- be sure to include links to your code, detailed results, and your reflection on the lab. == Week 6 == === Week 6 - Class I ===* [[Inline Assembly Language]] -- often used for:*# Implementing a memory barrier*# Performing an [[Atomic Operation]]*#* '''Atomics''' are operations which must be completed in a single step (or appear to be completed in a single step) without potential interruption.*#* Wikipedia has a good basic overview of the need for atomicity in the article on [http://en.wikipedia.org/wiki/Linearizability Linearizability]*# Gaining performance (by accessing processor features not exposed by the high-level language being used (C, C++, ...))* [[SPO600 Inline Assembler Lab|Inline Assembler Lab]] (Lab 6) === Week 6 - Class II ===* [[Addressing Mode|Processor Addressing Modes]]* Navigating CPU technical documentation* A (very) quick intro to GDB* [[Winter 2018 SPO600 Project|Project]]: Selecting, Building, Benchmarking, and Profiling === Week 6 Deliverables ===* Blog your Lab 5 and 6 results.* Start blogging about your project.* '''Reminder:''' Blogs will be marked as they stand at 11:59 on March 4, the Sunday at the end of Reading Week. == Week 7 == === Week 7 - Class I ===* Project Discussion === Week 7 - Class II ===* [[Profiling]] === Week 7 Deliverables ===* Complete your [[Winter_2018_SPO600_Project#Stage_1|Stage I]] project posts on your blog. == Week 8 == === Week 8 - Class I ===* Sysadmin for Developers* Project Discussion === Week 8 - Class II === ==== Overview/Review of Processor Operation ==== * Fetch-decode-dispatch-execute cycle* Pipelining* Branch Prediction* In-order vs. Out-of-order execution** Micro-ops ==== Memory Basics ==== * Organization of Memory** System organization** Process organization*** Text, data*** Stack*** Heap* Memory Speeds* Cache** Cache lookup** Cache synchronization and invalidation** Cache line size* Prefetch** Prefetch hinting ==== Memory Architecture ==== * Virtual Memory and Memory Management Units (MMUs)** General principles of VM and operation of MMUs** Memory protection*** Unmapped Regions*** Write Protection*** Execute Protection*** Privilege Levels** Swapping** Text sharing** Data sharing** Shared memory for Inter-Process Communication** Copy-on-Write (CoW)** Demand Loading** Memory mapped files === Software Impact ===* Alignment checks* Page boundary crossing === Week 8 Delivarables ===* Blog about your project == Week 9 == === Week 9 - Class I === ==== Atomics ====* '''Atomics''' are operations which must be completed in a single step (or appear to be completed in a single step) without potential interruption.** Wikipedia has a good basic overview of the need for atomicity in the article on [http://en.wikipedia.org/wiki/Linearizability Linerarizability]** Atomics may be performed using special instructions or Kernel-compiler cooperation ==== Memory Barriers ===='''Memory Barriers''' ensure that memory accesses are sequenced so that multiple threads, processes, cores, or IO devices see a predictable view of memory.* Leif Lindholm provides an excellent explanation of memory barriers.** Blog series - I recommend this series, especially the introduction, as a very clear explanation of memory barrier issues.*** Part 1 - [http://community.arm.com/groups/processors/blog/2011/03/22/memory-access-ordering--an-introduction Memory Access Ordering - An Introduction]*** Part 2 - [http://community.arm.com/groups/processors/blog/2011/04/11/memory-access-ordering-part-2--barriers-and-the-linux-kernel Memory Access Ordering Part 2 - Barriers and the Linux Kernel]*** Part 3 - [http://community.arm.com/groups/processors/blog/2011/10/19/memory-access-ordering-part-3--memory-access-ordering-in-the-arm-architecture Memory Access Ordering Part 3 - Memory Access Ordering in the ARM Architecture]** Presentation at Embedded Linux Conference 2010 (Note: Acquire/Release in C++11 and ARMv8 aarch64 appeared after this presentation):*** [http://elinux.org/images/f/fa/Software_implications_memory_systems.pdf Slides]*** [http://free-electrons.com/pub/video/2010/elce/elce2010-lindholm-memory-450p.webm Video]* [http://www.rdrop.com/users/paulmck/scalability/paper/whymb.2010.07.23a.pdf Memory Barriers - A Hardware View for Software Hackers] - This is a highly-rated paper that explains memory barrier issues - as the title suggests, it is designed to describe the hardware origin of the problem to software developers. Despite the fact that it is an introduction to the topic, it is still very technical.* [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.faqs/ka14041.html ARM Technical Support Knowlege Article - In what situations might I need to insert memory barrier instructions?] - Note that there are some additional mechanisms present in ARMv8 aarch64, including Acquire/Release.* [https://www.kernel.org/doc/Documentation/memory-barriers.txt Kernel Documentation on Memory Barriers] - discusses the memory barrier issue generally, and the solutions used within the Linux kernel. This is part of the kernel documentation.* Acquire-Release mechanisms** [http://blogs.msdn.com/b/oldnewthing/archive/2008/10/03/8969397.aspx MSDN Blog Post] with a very clear explanation of Acquire-Release.** [http://preshing.com/20130922/acquire-and-release-fences/ Preshing on Programming post] with a good explanation.** [http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.genc010197a/index.html ARMv8 Instruction Set Architecture Manual] (ARM InfoCentre registration required) - See the section on Acquire/Release and Load/Store, especially Load/Store Exclusive (e.g., LDREX) ==== The Future of Memory ====* NUMA (on steroids!)* Non-volatile, byte-addressed main memory* Non-local memory / Memory-area networks* Memory encryption ==== Building Software ====* Configuration Systems** make-based systems*** [https://www.gnu.org/software/automake/manual/html_node/index.html#Top The GNU Build System: autotools, autoconf, automake]*** Configuration name ("triplet") -- ''cpu-manufacturer-operatingSystem'' or ''cpu-manufacturer-kernel-operatingSystem''**** config.guess and config.sub*** CMake*** qmake*** Meson*** iMake and Others** Non-make-based systems*** Apache Ant*** Apache Maven*** Qt Build System* Building in the Source Tree vs. Building in a Parallel Tree** Pros and Cons** [https://www.gnu.org/software/automake/manual/html_node/VPATH-Builds.html#VPATH-Builds GNU automake ''vpath'' builds]* Installing and Testing in non-system directories** Configuring installation to a non-standard directory*** Running <code>configure</code> with <code>--prefix</code>*** Running <code>make install</code> as a non-root user*** DESTDIR variable for <code>make install</code>** Runtime environment variables:*** PATH*** LD_LIBRARY_PATH and LD_PRELOAD (see the [http://man7.org/linux/man-pages/man8/ld.so.8.html ld.so manpage])** Security when running software*** Device access**** Opening a TCP/IP or UDP/IP port below 1024**** Accessing a <code>/dev</code> device entry***** Root permission***** Group permission*** SELinux Type Enforcement**** Enforcement mode***** View enforcement mode: <code>getenforce</code>***** Set enforcement mode: <code>setenforce</code>**** Changing policy***** [https://fedoraproject.org/wiki/SELinux/audit2why audit2why]***** [https://fedoraproject.org/wiki/SELinux/audit2why audit2allow] === Week 9: Class II ===* Portability Issues === Week 9 Deliverables ===* Blog about your project == Week 10 == === Week 10: Class I ===* Project hacking and discussion === Week 10 Deliverables ===* Blog about your project.* Note: March blogs are due Monday, April 2. Remember that the target is 1-2 posts/week, which is 4-8 posts/month. == Week 11 == === Week 11 - Class I ===* Project hacking and discussion === Week 11 - Class II ===* [[Compiler Intrinsics]]* Project discussion == Week 12 == === Week 12 - Class I ===* Class cancelled === Week 12 - Class II ===* Project hacking and discussion <!-- ###############################################################################################################################################################################################################################################################################################################################################################################################################################
== Week 6 ==
* [[SPO600 Algorithm Selection Lab|Algorithm Selection Lab]] (Lab 6)
== Week 7 ==
=== Week 7 - Class I ===
Project discussion
=== Week 7 - Class II ===
Profiling
=== Week 7 Deliverables ===
Blog about your project.
=== Week 6 Deliverables ===
* Start blogging about your project!
=== Week 2 - Class II ===
* Blog about your selected function(s) and project plan
** Remember: You should be posting 1-2 times per week
#################################################################################
* Complete ALL your blogging for this course by Midnight on Thursday, April 21. Make sure that you have included all of the labs, your presentation, and your project work. Remember that there should be at least 1-2 posts per week. Your blogging from April 1-April 21 will be used for your April communication mark.
=== Tuesday (Sep 15) ===
