Changes between Version 30 and Version 31 of mapping_info


Ignore:
Timestamp:
Feb 15, 2015, 12:11:00 PM (9 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • mapping_info

    v30 v31  
    3131 * The kernel heap is distributed in all clusters. Each heap section is a ''vseg''.
    3232 * Finally there is a specific ''vseg'' for each peripheral (both internal and external), containing the peripheral addressable registers.
    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''.
    34 
    35 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'':
     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''.
     34
     353. 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'':
    3636 * 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. 
    3737 * 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).