Changes between Version 57 and Version 58 of replication_distribution


Ignore:
Timestamp:
Dec 20, 2019, 12:17:10 AM (2 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • replication_distribution

    v57 v58  
    183183This section describes the almost-mkh assumptions regarding the virtual space organisation. It clearly depends on the size of the virtual space. 
    184184
    185 === 5.1 TSAR-MIP32 ===
     185=== 5.1 Intel 64  ===
     186
     187TODO
     188
     189=== 5.2 TSAR-MIP32 ===
    186190
    187191The virtual address space of an user process P is split in 5 fixed size zones, defined by configuration parameters in [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/kernel_config.h].  Each zone contains one or several vsegs, as described below.
     
    210214
    211215It is located on top of the '''mmap''' zone and starts at the address defined by the [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/kernel_config.h CONFIG_VMM_STACK_BASE] parameter. It contains an array of fixed size slots, and each slot contains one ''stack'' vseg. The size of a slot is defined by the [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/kernel_config.h CONFIG_VMM_STACK_SIZE]. In each slot, the first page is not mapped, in order to detect stack overflows. As threads are dynamically created and destroyed, the VMM implements a specific STACK allocator for this zone, using a bitmap vector. As the ''stack'' vsegs are private (the same virtual address can have different mappings, depending on the cluster) the number of slots in the '''stack''' zone actually defines the max number of threads for given process in a given cluster.
    212 
    213 === 5.2 Intel 64  ===
    214 
    215 TODO