GitLab

Adding collective modeling functions in model-net (currently only dragonfly/torus models support it)

- NOTE: shim just forces packet size to a huge number

- NOTE: the current scheduling policy of FCFS is hard-coded, this will change
  in future revisions
- NOTE: random number generation has changed due to the differences in
  scheduling and packet ordering. Hence, results may be slightly different from
  runs prior to this commit

- pull itself not yet tested

Instead of specifying the loggp config file path relative to the
path of the respective executable file, you now must specify it
relative to the path of the master config file.

minor changes to model-net plug-in: (1) making the torus network's chunk size configurable (2) handling some edge cases which we haven't encountered so far but its good to have them for future

- these calls should be made by the top level model only, so that all
  results are consolidated into the same subdirectory
- add corresponding calls to modelnet test programs

also misc update to how loggp method plugs into modelnet

- just a copy of simplenet with variables and functions renamed for now

Adding statistics collection using lp-io in model-net API (comes from the simple-net stats collection), works for simple-net, torus and the dragonfly network models

Updates to modelnet (1) Updated the mapping configuration for dragonfly (the mapping now distributes the routers equally on all the PES.  The old dragonly mapping configuration was placing the routers on a single PE which was causing congestion on that PE leading to slow model performance in parallel ) (2) Updated 'make check' to handle dragonfly and torus test cases as well (3) Remove the num_servers argument from model-net test case, the number of servers are now calculated from the config file (4) Placing the ross mapping parameters in the codes mapping file

Adding dragonfly network model with codes, model-net-test case run time parameters are updated (see README_MN_TEST.txt for details)

Updates to modelnet torus plugin: reporting torus average+maximum latency and hops traversed via model-net API function

Adding the torus network plugin with modelnet API, see model-net/README_MN_TEST.txt for instructions to run the test

Updates to model-net test program based on the new config file format. We can now configure all network parameters from the config file