Publish refs/pull/392/merge

Author: GitHub Actions

refs/pull/392/merge/_sources/lectures/debugging.rst.txt

@@ -923,7 +923,7 @@ perf
 
    * performance counters, tracepoints, kprobes, uprobes
    * hardware events: CPU cycles, TLB misses, cache misses
-   * software events: page fauls , context switches
+   * software events: page faults , context switches
    * collects backtraces (user + kernel)
 
 Other tools

refs/pull/392/merge/_sources/so2/assign-collaboration.rst.txt

@@ -121,7 +121,7 @@ Follow the seven rules of writing a good commit message: https://cbea.ms/git-com
 Add `TODOs` with each team member tasks. Try to split the work evenly.
 
 Before starting to code, make a plan. On top of your skeleton file, add TODOs with each member tasks. Agree on global
-structures and the overlall driver design. Then start coding.
+structures and the overall driver design. Then start coding.
 
 5. Do reviews
 -------------

refs/pull/392/merge/_sources/so2/assign3-software-raid.rst.txt

@@ -2,7 +2,7 @@
 Assignment 3 - Software RAID
 ===========================
 
-- Deadline: :command:`Monday, 15 May 2023, 23:00`
+- Deadline: :command:`Monday, 15 May 2024, 23:59`
 - This assignment can be made in teams (max 2). Only one of them must submit the assignment, and the names of the student should be listed in a README file.
 
 Implementing a software RAID module that uses a logical block device that will read and write data from two physical devices,

refs/pull/392/merge/lectures/debugging-slides.html

@@ -793,7 +793,7 @@ <h2>perf</h2>
 <ul class="simple">
 <li>performance counters, tracepoints, kprobes, uprobes</li>
 <li>hardware events: CPU cycles, TLB misses, cache misses</li>
-<li>software events: page fauls , context switches</li>
+<li>software events: page faults , context switches</li>
 <li>collects backtraces (user + kernel)</li>
 </ul>
 

refs/pull/392/merge/lectures/debugging.html

@@ -850,7 +850,7 @@ <h2>perf<a class="headerlink" href="#perf" title="Permalink to this headline">¶
 <ul class="admonition-perf simple">
 <li>performance counters, tracepoints, kprobes, uprobes</li>
 <li>hardware events: CPU cycles, TLB misses, cache misses</li>
-<li>software events: page fauls , context switches</li>
+<li>software events: page faults , context switches</li>
 <li>collects backtraces (user + kernel)</li>
 </ul>
 </div>

refs/pull/392/merge/searchindex.js

@@ -277,7 +277,7 @@ <h2>3. Add a commit for each individual change<a class="headerlink" href="#add-a
 <h2>4. Split the work inside the team<a class="headerlink" href="#split-the-work-inside-the-team" title="Permalink to this headline">¶</a></h2>
 <p>Add <cite>TODOs</cite> with each team member tasks. Try to split the work evenly.</p>
 <p>Before starting to code, make a plan. On top of your skeleton file, add TODOs with each member tasks. Agree on global
-structures and the overlall driver design. Then start coding.</p>
+structures and the overall driver design. Then start coding.</p>
 </div>
 <div class="section" id="do-reviews">
 <h2>5. Do reviews<a class="headerlink" href="#do-reviews" title="Permalink to this headline">¶</a></h2>

refs/pull/392/merge/so2/assign-collaboration.html

@@ -178,7 +178,7 @@
   <div class="section" id="assignment-3-software-raid">
 <h1>Assignment 3 - Software RAID<a class="headerlink" href="#assignment-3-software-raid" title="Permalink to this headline">¶</a></h1>
 <ul class="simple">
-<li>Deadline: <strong class="command">Monday, 15 May 2023, 23:00</strong></li>
+<li>Deadline: <strong class="command">Monday, 15 May 2024, 23:59</strong></li>
 <li>This assignment can be made in teams (max 2). Only one of them must submit the assignment, and the names of the student should be listed in a README file.</li>
 </ul>
 <p>Implementing a software RAID module that uses a logical block device that will read and write data from two physical devices,

refs/pull/392/merge/so2/assign3-software-raid.html

@@ -803,7 +803,7 @@ <h2>perf</h2>
 <ul class="simple">
 <li>performance counters, tracepoints, kprobes, uprobes</li>
 <li>hardware events: CPU cycles, TLB misses, cache misses</li>
-<li>software events: page fauls , context switches</li>
+<li>software events: page faults , context switches</li>
 <li>collects backtraces (user + kernel)</li>
 </ul>
 

refs/pull/392/merge/so2/lec9-debugging-slides.html

@@ -881,7 +881,7 @@ <h2>perf<a class="headerlink" href="#perf" title="Permalink to this headline">¶
 <ul class="admonition-perf simple">
 <li>performance counters, tracepoints, kprobes, uprobes</li>
 <li>hardware events: CPU cycles, TLB misses, cache misses</li>
-<li>software events: page fauls , context switches</li>
+<li>software events: page faults , context switches</li>
 <li>collects backtraces (user + kernel)</li>
 </ul>
 </div>