Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/proposals/concurrency/annex/glossary.tex

    rcf966b5 r3364962  
    44{name={callsite-locking}}
    55{
    6 Locking done by the calling routine. With this technique, a routine calling a monitor routine aquires the monitor \emph{before} making the call to the actuall routine.
     6Locking done by the calling routine. With this technique, a routine calling a monitor routine will aquire the monitor \emph{before} making the call to the actuall routine.
    77}
    88
     
    1010{name={entry-point-locking}}
    1111{
    12 Locking done by the called routine. With this technique, a monitor routine called by another routine aquires the monitor \emph{after} entering the routine body but prior to any other code.
     12Locking done by the called routine. With this technique, a monitor routine called by another routine will aquire the monitor \emph{after} entering the routine body but prior to any other code.
    1313}
    1414
     
    2222{name={multiple-acquisition}}
    2323{
    24 Any locking technique that allows a single thread to acquire the same lock multiple times.
     24Any locking technique which allow any single thread to acquire a lock multiple times.
    2525}
    2626
     
    3535{name={user-level thread}}
    3636{
    37 Threads created and managed inside user-space. Each thread has its own stack and its own thread of execution. User-level threads are invisible to the underlying operating system.
     37Threads created and managed inside user-space. Each thread has its own stack and its own thread of execution. User-level threads are insisible to the underlying operating system.
    3838
    3939\textit{Synonyms : User threads, Lightweight threads, Green threads, Virtual threads, Tasks.}
     
    5151{name={fiber}}
    5252{
    53 Fibers are non-preemptive user-level threads. They share most of the caracteristics of user-level threads except that they cannot be preempted by another fiber.
     53Fibers are non-preemptive user-level threads. They share most of the caracteristics of user-level threads except that they cannot be preempted by an other fiber.
    5454
    5555\textit{Synonyms : Tasks.}
     
    5959{name={job}}
    6060{
    61 Unit of work, often sent to a thread pool or worker pool to be executed. Has neither its own stack nor its own thread of execution.
     61Unit of work, often send to a thread pool or worker pool to be executed. Has neither its own stack or its own thread of execution.
    6262
    6363\textit{Synonyms : Tasks.}
     
    7575{name={cluster}}
    7676{
    77 A group of \gls{kthread} executed in isolation.
     77TBD...
     78
     79\textit{Synonyms : None.}
     80}
     81
     82\longnewglossaryentry{cfacpu}
     83{name={processor}}
     84{
     85TBD...
    7886
    7987\textit{Synonyms : None.}
     
    8391{name={thread}}
    8492{
    85 User level threads that are the default in \CFA. Generally declared using the \code{thread} keyword.
     93TBD...
    8694
    8795\textit{Synonyms : None.}
     
    9199{name={preemption}}
    92100{
    93 Involuntary context switch imposed on threads at a specified rate.
     101TBD...
    94102
    95103\textit{Synonyms : None.}
Note: See TracChangeset for help on using the changeset viewer.