Changes between Version 16 and Version 17 of mapping_info

Timestamp:

Oct 28, 2014, 11:34:55 AM (10 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -80 +80 @@
 || p      || physical memory bank size (bytes) ||
 
-The physical global processor index will be : ( ( x << y_width ) + y ) << p_width ) + p
+The global processor index is : ( ( x << y_width ) + y ) << p_width ) + p
 
 === 3. Physical memory bank ===
@@ -137 +137 @@
 
 The supported values for the ''mode'' argument, and for the ''vtype'' arguments are defined in the [source:soft/giet_vm/giet_python/mapping.py mapping.py] file.
-The ''x'', ''y'', and ''pseg'' arguments define actually the mapping.
+
+The (''x'', ''y'', ''pseg')' arguments define actually the vseg placement.
 
 === 1. Boot vsegs ===
 
-There is 4 'vsegs for the GIET_VM bootloader:
+There is 4  global vsegs for the GIET_VM bootloader:
  * The '''seg_boot_mapping''' vseg contains the C binary structure defining the mapping. It is loaded from disk by the boot-loader.
  * The '''seg_boot_code''' vseg contains the boot-loader code. It is loaded from disk by the preloader.
@@ -150 +151 @@
 === 2. Kernel vsegs ===
 
-There is six types of vsegs for the GIET_VM kernel, but some vsegs are replicated in all clusters, to improve locality and minimize contention, as explained below:
+There is six types of global vsegs for the GIET_VM kernel, but some vsegs are replicated in all clusters, to improve locality and minimize contention, as explained below:
  * The '''seg_kernel_ptab_x_y''' vseg has type PTAB. It contains the page tables for all vspaces (one page table per vspace). There is one such vseg in each cluster (one set of page tables per cluster). Each PTAB vseg is mapped in one big physical page. 
  * The '''seg_kernel_code''' & '''seg_kernel_init''' have type ELF. They contain the kernel code. These two vsegs must be mapped in one big physical page. They are  replicated in each cluster. The ''local'' attribute must be set, because the same virtual address will be mapped on different physical address depending on the cluster.   
@@ -168 +169 @@
 
 There is several types of user vseg  
- * The '''code''' vseg can be optionally replicated in all clusters. 
+ * The '''code''' vseg can be (optionally) replicated in all clusters. 
  * The '''data''' vseg is not replicated. It must contain the ''start_vector'' defining the entry points of the application tasks.
  * It must exist as many '''stack'''' vseg as the number of tasks. 
- * One or several '''heap''' vseg(s), can be used by the malloc user library.
- * One or several '''mwmr''' vseg(s)
+ * One or several '''heap''' vseg(s), can be used by the ''malloc'' user library.
+ * One or several '''mwmr''' vseg(s) can be used by the ''mwmr'' user library.
  
 === 1. create the vspace ===
@@ -178 +179 @@
 The '''mapping.addvspace( )''' construct define a vspace. It has the following arguments:
 || name        || vspace name == application name  ||
-|| startname || name of              || 
+|| startname || name of vseg containing the start_vector   || 
 
 ===  2. vseg mapping ===
@@ -198 +199 @@
 
 The supported values for the ''mode'' argument, and for the ''vtype'' arguments are defined in the [source:soft/giet_vm/giet_python/mapping.py mapping.py] file.
-The ''x'', ''y'', and ''pseg'' arguments define actually the mapping.
+
+The (''x'', ''y'', ''pseg')' arguments define actually the vseg placement.
 
 === 3. task mapping ===
@@ -209 +211 @@
 || y                || destination cluster Y coordinate ||
 || lpid            || destination processor local index ||
-|| stackname || name of vseg containing stack ||
-|| heapname  || name of vseg containing heap ||
+|| stackname || name of vseg containing the task stack ||
+|| heapname  || name of vseg containing the task heap ||
 || startid        || index in start vector (defining the task entry point virtual address) ||