Changes between Version 3 and Version 4 of CapabilitiesAndScheduling


Ignore:
Timestamp:
May 19, 2006 1:41:35 PM (8 years ago)
Author:
guest
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CapabilitiesAndScheduling

    v3 v4  
    168168 
    169169Here are some important observations about a capability: it consists of essentially a collection of OS threads, a register set and a set of TSOs. The resister set is the member of type 'r'. Real hardware may or may not provide mappings of these to actual registers. [Anything else to add here?]. 
     170 
     171== TSO == 
    170172 
    171173TSO stands for Thread State Object and is the abstract for a haskell thread from the perspective of the RTS. TSO's are defined in TSO.h.  
     
    214216}}} 
    215217 
    216  
     218Probabky the single most important part of a TSo from the perspectice of the GC is the stack that it contains. This stack is essentially the 'roots of the program'. 
     219 
     220== Terminology ==  
     221 
     222This is a good point to introduce some terminology related to the above -  
     223 
     224 * task - is essentially an OS thread executing a forgein function call. The haskell thread that needed to execute the FFI call is attached to this thread for the entire duration of the forgein call. [is there something more that I can say here?] 
     225 
     226 *