Changes between Version 31 and Version 32 of mapping_info

Timestamp:

Feb 15, 2015, 12:13:21 PM (9 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -17 +17 @@
 The mapping contains the following informations:
 
-1.  The mapping contains a description of the target, clusterized, hardware architecture, with the following constraints: 
+1.  It contains a description of the target, clusterized, hardware architecture, with the following constraints: 
  * All processor cores are identical (MIPS32). 
  * The clusters form a 2D mesh topology. The mesh size is defined by the (X_SIZE,Y_SIZE) parameters. 
@@ -26 +26 @@
  * The physical address is the concatenation of 3 fields: the LSB field (32 bits) define a 4 Gbits physical address space inside a single cluster. The X  and Y MSB fields (up to 4 bits for each field) define the cluster coordinates.
 
-2. the mapping contains a description of the GIET_VM kernel software objects (called virtual segments or ''vsegs''):
+2. It contains a description of the GIET_VM kernel software objects (called virtual segments or ''vsegs''):
  * The kernel code is replicated in all clusters. Each copy is a ''vseg''. 
  * There is one page table for each user application, and this page table is replicated in each cluster. Each copy is a ''vseg''. 
@@ -33 +33 @@
  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 application(s) 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 depends on the target architecture, and 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'':
+3. It  contains a description of the user application(s) 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 depends on the target architecture, and 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).