Changes between Version 24 and Version 25 of mapping_info

Timestamp:

Feb 14, 2015, 11:16:57 PM (9 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -31 +31 @@
  * The kernel heap is distributed in all clusters. Each heap section is a ''vseg''.
  * Finally there is a specific ''vseg'' for each peripheral (both internal and external), containing the peripheral addressable registers. 
-All these vsegs being accessed by all user applications must be defined in all virtual spaces, and are mapped in all page tables. They are called ''globa' vsegs''. 
-
-3. The mapping  contains a description of the user applications to be launched on the platform. An user application is characterized by a a virtual address space, called a ''vspace''. An user application can be multi-threaded, and the number of parallel tasks sharing the same address space in a given application is variable (can be one). Each task must be statically placed on a processor P(x,y,p). Moreover, each application defines a variable number of ''vsegs'':
+All these kernel ''vsegs'' being accessed by all user applications must be defined in all virtual spaces, and are mapped in all page tables. They are called ''global vsegs''. 
+
+3. The mapping  contains a description of the user applications to be launched on the platform. An user application is characterized by a a virtual address space, called a ''vspace''. An user application can be multi-threaded. The number of parallel tasks sharing the same address space in a given application can be adapted to the target architecture, but each task must be statically placed on a given processor (p) in a given cluster(x,y). Moreover, each application defines a variable number of ''vsegs'':
  * The application code can be defined as a single ''vseg'', placed in a single cluster. It can also be replicated in all clusters, with one ''vseg''  per cluster.  
  * There is one stack for each application task. There is one ''vseg'' per stack, and each stack ''vseg'' must be placed in a specific cluster(x,y). 
  * The data ''vseg'' contains the global (shared) variables. It is not replicated, and must be placed in a single cluster.
- * The user heap can be physically distributed on all clusters and it can exist one  heap ''vseg'' per cluster.as many ''vsegs''.
+ * The user heap can be physically distributed on all clusters and it can exist one  heap ''vseg'' per cluster.
 
 == __C mapping data structure__ ==