Changes between Version 56 and Version 57 of WikiStart


Ignore:
Timestamp:
Nov 5, 2014, 12:47:28 PM (10 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • WikiStart

    v56 v57  
    33The GIET_VM is a fully '''static operating system''' for shared address space, many-cores architectures. These architectures are generally  NUMA (Non Uniform memory Acces), because the memory is logically shared, but physically distributed, and the main goal of the GIET_VM is to address these NUMA issues.
    44
    5 The GIET-VM assumes that there is one physical memory bank, and several processor cores per cluster. Each processor is identified by a composite index [x,y,p] where (x,y) are the cluster coordinates, and p is the local processor index.
     5The GIET-VM assumes that the hardware architecture is structured as a 2D mesh of ''clusters''. There is one physical memory bank, and several processor cores per cluster. Each processor is identified by a composite index [x,y,p] where x, y are the cluster coordinates, and p is the local processor index.
    66
    7 It is written for the MIPS32 processor. The virtual adresses are on 32 bits and use the (unsigned int) type, but the physicals addresses can have up to 40 bits, and use the (unsigned long long) type.
     7It is written for the MIPS32 processor. The virtual adresses are on 32 bits and use the (unsigned int) type, but the physicals addresses can have up to 40 bits, and use the (unsigned long long) type.
     8
     9The target architecture is generic, and the parameter values (such as the number of clusters, or the number of cores per cluster) are defined in the [source:soft/giet_vm/hard_config.h hard_config.h] file. The GIET-VM itself has configuration parameters that are defined in the [source:soft/giet_vm/giet_config.h giet_config.h] file.
    810
    911== __A) [wiki:mapping_info Mapping]__ ==
     12
     13Both the target hardware architecture and the mapping directives (placement of software tasks on the physical processors / placement of the software objects on the physical memory banks) must be described in a python script. This section describes the Python constructs used to describe the mapping.
    1014
    1115== __B) [wiki:boot_loader Boot-loader]__ ==