source: doc/theses/thierry_delisle_PhD/thesis/text/practice.tex @ bfd5512

Last change on this file since bfd5512 was bfd5512, checked in by Thierry Delisle <tdelisle@…>, 6 months ago

Pushing what little I have for Chapter 5

  • Property mode set to 100644
File size: 7.5 KB
1\chapter{Scheduling in practice}\label{practice}
2The scheduling algorithm discribed in Chapter~\ref{core} addresses scheduling in a stable state.
3However, it does not address problems that occur when the system changes state.
4Indeed the \CFA runtime, supports expanding and shrinking the number of \procs, both manually and, to some extent, automatically.
5This entails that the scheduling algorithm must support these transitions.
7More precise \CFA supports adding \procs using the RAII object @processor@.
8These objects can be created at any time and can be destroyed at any time.
9They are normally create as automatic stack variables, but this is not a requirement.
11The consequence is that the scheduler and \io subsystems must support \procs comming in and out of existence.
13\section{Manual Resizing}
14The consequence of dynamically changing the number of \procs is that all internal arrays that are sized based on the number of \procs neede to be \texttt{realloc}ed.
15This also means that any references into these arrays, pointers or indexes, may need to be fixed when shrinking\footnote{Indexes may still need fixing because there is no guarantee the \proc causing the shrink had the highest index. Therefore indexes need to be reassigned to preserve contiguous indexes.}.
17There are no performance requirements, within reason, for resizing since this is usually considered as part of setup and teardown.
18However, this operation has strict correctness requirements since shrinking and idle sleep can easily lead to deadlocks.
19It should also avoid as much as possible any effect on performance when the number of \procs remain constant.
20This later requirement prehibits simple solutions, like simply adding a global lock to these arrays.
23One solution is to use the Read-Copy-Update\cite{wiki:rcu} pattern.
24In this pattern, resizing is done by creating a copy of the internal data strucures, updating the copy with the desired changes, and then attempt an Idiana Jones Switch to replace the original witht the copy.
25This approach potentially has the advantage that it may not need any synchronization to do the switch.
26The switch definitely implies a race where \procs could still use the previous, original, data structure after the copy was switched in.
27The important question then becomes whether or not this race can be recovered from.
28If the changes that arrived late can be transferred from the original to the copy then this solution works.
30For linked-lists, dequeing is somewhat of a problem.
31Dequeing from the original will not necessarily update the copy which could lead to multiple \procs dequeing the same \at.
32Fixing this requires making the array contain pointers to subqueues rather than the subqueues themselves.
34Another challenge is that the original must be kept until all \procs have witnessed the change.
35This is a straight forward memory reclamation challenge but it does mean that every operation will need \emph{some} form of synchronization.
36If each of these operation does need synchronization then it is possible a simpler solution achieves the same performance.
37Because in addition to the classic challenge of memory reclamation, transferring the original data to the copy before reclaiming it poses additional challenges.
38Especially merging subqueues while having a minimal impact on fairness and locality.
40\subsection{Read-Writer Lock}
41A simpler approach would be to use a \newterm{Readers-Writer Lock}\cite{wiki:rwlock} where the resizing requires acquiring the lock as a writer while simply enqueing/dequeing \ats requires acquiring the lock as a reader.
42Using a Readers-Writer lock solves the problem of dynamically resizing and leaves the challenge of finding or building a lock with sufficient good read-side performance.
43Since this is not a very complex challenge and an ad-hoc solution is perfectly acceptable, building a Readers-Writer lock was the path taken.
45To maximize reader scalability, the readers should not contend with eachother when attempting to acquire and release the critical sections.
46This effectively requires that each reader have its own piece of memory to mark as locked and unlocked.
47Reades then acquire the lock wait for writers to finish the critical section and then acquire their local spinlocks.
48Writers acquire the global lock, so writers have mutual exclusion among themselves, and then acquires each of the local reader locks.
49Acquiring all the local locks guarantees mutual exclusion between the readers and the writer, while the wait on the read side prevents readers from continously starving the writer.
50\todo{reference listings}
53void read_lock() {
54        // Step 1 : make sure no writers in
55        while write_lock { Pause(); }
57        // May need fence here
59        // Step 2 : acquire our local lock
60        while atomic_xchg( tls.lock ) {
61                Pause();
62        }
65void read_unlock() {
66        tls.lock = false;
71void write_lock()  {
72        // Step 1 : lock global lock
73        while atomic_xchg( write_lock ) {
74                Pause();
75        }
77        // Step 2 : lock per-proc locks
78        for t in all_tls {
79                while atomic_xchg( t.lock ) {
80                        Pause();
81                }
82        }
85void write_unlock() {
86        // Step 1 : release local locks
87        for t in all_tls {
88                t.lock = false;
89        }
91        // Step 2 : release global lock
92        write_lock = false;
97In addition to users manually changing the number of \procs, it is desireable to support ``removing'' \procs when there is not enough \ats for all the \procs to be useful.
98While manual resizing is expected to be rare, the number of \ats is expected to vary much more which means \procs may need to be ``removed'' for only short periods of time.
99Furthermore, race conditions that spuriously lead to the impression no \ats are ready are actually common in practice.
100Therefore \procs should not be actually \emph{removed} but simply put into an idle state where the \gls{kthrd} is blocked until more \ats become ready.
101This state is referred to as \newterm{Idle-Sleep}.
103Idle sleep effectively encompasses several challenges.
104First some data structure needs to keep track of all \procs that are in idle sleep.
105Because of idle sleep can be spurious, this data structure has strict performance requirements in addition to the strict correctness requirements.
106Next, some tool must be used to block kernel threads \glspl{kthrd}, \eg \texttt{pthread\_cond\_wait}, pthread semaphores.
107The complexity here is to support \at parking and unparking, timers, \io operations and all other \CFA features with minimal complexity.
108Finally, idle sleep also includes a heuristic to determine the appropriate number of \procs to be in idle sleep an any given time.
109This third challenge is however outside the scope of this thesis because developping a general heuristic is involved enough to justify its own work.
110The \CFA scheduler simply follows the ``Race-to-Idle'\cit{}' approach where a sleeping \proc is woken any time an \at becomes ready and \procs go to idle sleep anytime they run out of work.
113\section{Tracking Sleepers}
114Tracking which \procs are in idle sleep requires a data structure holding all the sleeping \procs, but more importantly it requires a concurrent \emph{handshake} so that no \at is stranded on a ready-queue with no active \proc.
115The classic challenge is when a \at is made ready while a \proc is going to sleep, there is a race where the new \at may not see the sleeping \proc and the sleeping \proc may not see the ready \at.
117Furthermore, the ``Race-to-Idle'' approach means that there is some
121\subsection{Event FDs}
127\section{Reducing Latency}
Note: See TracBrowser for help on using the repository browser.