Apr 13, 2022, 1:08:44 PM (23 months ago)
Thierry Delisle <tdelisle@…>
ADT, ast-experimental, enum, master, pthread-emulation, qualifiedEnum

Some more writing, mostly pushing to have it on other machines

1 edited


  • doc/theses/thierry_delisle_PhD/thesis/text/practice.tex

    r3112733 r6b06abe  
    22The scheduling algorithm discribed in Chapter~\ref{core} addresses scheduling in a stable state.
    33However, it does not address problems that occur when the system changes state.
    4 Indeed the \CFA runtime, supports expanding and shrinking the number of KTHREAD\_place \todo{add kthrd to glossary}, both manually and, to some extent automatically.
     4Indeed the \CFA runtime, supports expanding and shrinking the number of \procs, both manually and, to some extent, automatically.
    55This entails that the scheduling algorithm must support these transitions.
    7 \section{Resizing}
     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;
     98\subsection{Tracking Sleepers}
     100\subsection{Event FDs}
     106\subsection{Reducing Latency}
Note: See TracChangeset for help on using the changeset viewer.