Changes between Version 32 and Version 33 of mapping_info

Timestamp:

Feb 15, 2015, 2:04:53 PM (9 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -190 +190 @@
 
 There is several types of user vseg: 
- * The '''code''' vsegs must have type ELF. They can be (optionally) replicated in all clusters. 
- * The '''data''' vseg must have type ELF. It 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 private stack per task). They have type BUFFER, and should be placed in the cluster containing the processor running the task. 
- * One or several '''heap''' vseg(s), can be used by the ''malloc'' user library. They must have type HEAP.
- * One or several '''mwmr''' vseg(s) can be used by the ''mwmr'' user library. They must have type BUFFER.
+ * The '''code''' vsegs must have the ELF type. They can be (optionally) replicated in all clusters. 
+ * The '''data''' vseg must have the ELF type. It is not replicated and must be mapped in one single cluster. It contains the ''start_vector'' defining the entry points of the application tasks.
+ * It must exist as many '''stack'''' vseg as the number of tasks (one private stack per task). They have the BUFFER type. Each stack vseg should be placed in the cluster containing the processor running the associated task. 
+ * The distributed '''heap''' vsegs (one vseg per cluster), are handled by the ''malloc'' user library. These vsegs must have the HEAP type. The ''remote_malloc()'' can be used to control the placement of specific data on the physical memory banks.
  
 === 1. create the vspace ===
@@ -210 +209 @@
 || '''size'''         || vseg size (bytes) ||
 || '''mode'''      || access rights (CXWU) ||
-|| '''vtype'''       || vseg type ||
+|| '''vtype'''       || vseg type ||
 || '''x'''              || destination cluster X coordinate ||
 || '''y'''              || destination cluster Y coordinate ||