details:
- instr_routing_define_callbacks defines a set of callbacks to the parser
- each level of the platform hierarchy becomes a new type
example: a three level simgrid platform hierarchy will have
container type L1 (child of root), container type L2 (child of L1)
container type L3 (child of L2).
- each AS becomes a container (its type is defined according to its level)
example: if a three level simgrid platform hierarchy is given, with
one AS in the first level (id: Site),
two in the second (ids: X, Y),
two in the third, for each of the second (ids: X1, X2, Y1, Y2)
The tracing will create:
a container of type L1, named Site (child of root)
two containers of type L2, X and Y (both child of Site)
four containers of type L3, X1 and X2 (child of X), and Y1, Y2 (child of Y)
- ROUTER is a new container type for routers
- containers of type HOST, LINK, and ROUTER can be in any level of the type hierarchy:
for each AS, a unique type alias is created for each of them,
but the type name for all of them remains HOST, LINK and ROUTER)
- the tracing mechanism now holds a (static) structure of the platform hierarchy
that is used during the simulation
git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@9158
48e7efb5-ca39-0410-a469-
dd3cf9ba447f
