Changes between Version 38 and Version 39 of mapping_info


Ignore:
Timestamp:
Sep 26, 2015, 10:19:43 AM (9 years ago)
Author:
alain
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • mapping_info

    v38 v39  
    205205The '''mapping.addvspace( )''' construct define a vspace. It has the following arguments:
    206206|| '''name'''        || vspace name == application name  ||
    207 || '''startname''' || name of vseg containing the start_vector   ||
     207|| '''startname''' || name of vseg containing the start_vector defining the entry points for all threads  ||
     208|| '''active'''       || boolean defining if the application should be activated by the boot code (default is False) ||
    208209
    209210===  2. vseg mapping ===
     
    227228The (''x'', ''y'', ''pseg'') arguments define actually the vseg placement.
    228229
    229 === 3. task mapping ===
    230 
    231 The '''mapping.addTask( )''' construct  defines the mapping of  a task on a processor. It has the following arguments:
    232 || '''vspace'''       || vspace containing the task ||
    233 || '''name'''         || task name (unique in vspace) ||
    234 || '''trdid'''          || thread index (unique in vspace] ||
     230=== 3. thread mapping ===
     231
     232The '''mapping.addThread( )''' construct  defines the static mapping of  a thread on a processor. It has the following arguments:
     233|| '''vspace'''       || vspace containing the thread ||
     234|| '''name'''         || thread name (unique in vspace) ||
     235|| '''is_main'''      || Boolean defining the thread that must be activated to launch the application ||
    235236|| '''x'''                || destination cluster X coordinate ||
    236237|| '''y'''                || destination cluster Y coordinate ||
    237 || '''lpid'''            || destination processor local index ||
    238 || '''stackname''' || name of vseg containing the task stack ||
    239 || '''heapname'''  || name of vseg containing the task heap ||
    240 || '''startid'''        || index in start vector (defining the task entry point virtual address) ||
    241 
    242 The (''x'', ''y'', ''lpid'') arguments define actually the task placement.
    243 
    244 
    245 
    246 
     238|| '''p'''                || destination processor local index ||
     239|| '''stackname''' || name of vseg containing the thread stack ||
     240|| '''heapname'''  || name of vseg containing the thread heap ||
     241|| '''startid'''        || index in start vector (defining the thread entry point virtual address) ||
     242
     243The (''x'', ''y'', ''p'') arguments define actually the thread placement.
     244
     245
     246
     247