Proposal to the mapping section in GRP file ( !old : 16nov95! ) : 
Section: Mapping
{
  Group: MappOptions
  {
    static_speed = 2
    dynamic = 0
  }
  Group: TaskGraph
  {
    ntask = 7
    nchan = 12
    load  = 2 1 1 1 1 1 1
    comm  = 0 1 1  0 2 1  0 3 1  0 4 1  0 5 1  0 6 1  0 7 1
    comm  = 1 0 1  2 0 1  3 0 1  4 0 1 	5 0 1  6 0 1  7 0 1
  }
  Group: ProcessorGraph
  {
    nproc = 4
    pvm_name  = ups savba sierra sfinx
    speed = 400 150 350 950
    comm  =  0 0 1  0 1 4  0 2 1  0 3 12
    comm  =  1 0 5  1 1 3  1 2 4  1 3 5
    comm  =  2 0 3  2 1 4  2 2 1  2 3 6
    comm  =  3 0 7  3 1 8  3 2 7  3 3 1
  }
}
The mapping section includes MappingOption, where can be two parameters:
  • the choosen static mapping method (greedy/iterative/huge..., i.e. 0/1/2...) PSmore...
  • the switch if the dynamic load-balancing should take place (i.e. 0/1)

    We need to know the task structure, i.e. task graph. In our proposal there can be

  • number of parallel-running tasks
  • (perhaps their names : task_name = master slave1 slave2 ...)
  • number of communication channels (channel is one-directional)
  • load value for each task
  • communication traffic between all the connected task pairs

    We also need to know the hardware structure, i.e. processor graph. There can be in this group

  • number of PVM hosts (nproc)
  • their names (our tool can estimate some data from PVM and store them :-)
  • their computational power
  • their interconnection costs (the diagonale values mean the inter-node comm. costs)

    The output that mapping tool creates can be written in the Result group as follows: 

    Section: Mapping
{
  Group: Result
  {
    location = 0 1 2 3 1 2 3
    imbalance = 1.34
    comm_cost = 254
    method = diffu
  }

}
    I propose to use third possibility of "how return mapping results to the task" - direct to the compiled "a.out" binary as extern data file, i.e. task need not be recompiled (grapnel nor cc). This extern file can have the same looks as the line "location = ..." or as whole group in the mapping section.

    Questions to the GRAPNEL-definition & GRED people:

  • what about vector values? => is possible?, delimiter, braces ...
  • what about text line length? => should lines be cutted by proposed form? ( repeated value name and '=' )

    Questions to the Mapping and Simulation people:

  • do you agree with this format (suitable for GRAPNEL language)?
  • are these data sufficient (suggest your requirements)
  • -> we had agreed on the format, but world is changing :-(