Changes between Version 40 and Version 41 of mapping_info

Timestamp:

Sep 26, 2015, 10:43:40 AM (9 years ago)

Author:

alain

Comment:

--

mapping_info

@@ -27 +27 @@
 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. All page tables are packed in one single ''vseg'', and this ''vseg'' is
-replicated in each cluster. 
+ * There is one page table for each user application. All page tables are packed in one single ''vseg'', and this ''vseg'' is replicated in each cluster. 
  * 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 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. 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 user threads respect the POSIX API.The number of threads can depend on the target architecture. Each thread must be statically placed on a given processor (x,y,p). Moreover, each application defines a variable number of ''vsegs'':
@@ -38 +36 @@
  * 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.
+
+All 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''. 
 
 == __C mapping data structure__ ==