Changes between Version 12 and Version 13 of mapping_info

Timestamp:

Oct 27, 2014, 5:45:33 PM (10 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -3 +3 @@
 [[PageOutline]]
 
-The GIET_VM is a fully '''static operating system''' supporting clusterized, shared address space, many-cores architectures. These architecture 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. 
-
-the GIET_VM bootloader map one or several multi-threaded user applications on the target architecture. 
+The GIET_VM is a fully '''static operating system''' for shared address space, many-cores architectures. These architecture 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. 
+
+the GIET_VM bootloader map the kernel and one or several multi-threaded user applications on the target architecture. 
 All software objects (user applications code and data, but also kernel code and critical kernel structures such as the page tables or the processors schedulers) are statically build and loaded from disk into physical memory by the GIET_VM bootloader in the boot phase. 
 
-The main advantage of this static approach is to provide the system designed a full control on the placement of tasks on processors but also of the data (software objects) on the distributed physical memory banks. It supports replication of (read-only) critical objects such as kernel code, user code, or page tables (the page tables are statically initialised in the boot phase, and are not modified anymore in the execution phase).
+The main advantage of this static approach is to provide the system designer to place the tasks on the processors, but also to place software objects on the distributed physical memory banks. It supports replication of (read-only) critical objects such as kernel code, user code, or page tables. The page tables are statically initialised in the boot phase, and are not modified anymore in the execution phase.
 
 To define the mapping, the system designer must provide a '''map.bin''' file containing a dedicated C binary data structure, that is loaded in memory by the bootloader.