1. 14 May, 2019 1 commit
    • Neil McGlohon's avatar
      Update all usage of "server" lp to "nw-lp" · 71f2692b
      Neil McGlohon authored
      Update all usage of "server" lp to "nw-lp"
      This change is made for consistency across all configuration files
      and workload generators in core CODES. Where older models and versions
      of CODES utilized the "server" identifier to specify the number of
      server LPs per modelnet group repetition, newer models and
      configurations utilized the less paradigm specific "nw-lp" identifier.
      This shift slightly fractured the codebase and led to confusion when
      running similar/same configurations across different network models.
      Specifically, this change converts all usage of the "server" identifier
      to the "nw-lp" identifier. All tests, existing default configuration
      files, and models have been updated to use the "nw-lp" identifier for
      the workload server LPs. Some docs and readmes have been updated as well
      to no longer instruct new users to use the "server" identifier.
  2. 13 Jul, 2016 1 commit
  3. 08 Jan, 2016 1 commit
  4. 29 Aug, 2014 1 commit
  5. 31 Jul, 2014 1 commit
    • Jonathan Jenkins's avatar
      config overhaul + annotation-aware mapping · 4e19d940
      Jonathan Jenkins authored
      All configuration now proceeds on a per-LP level, and requires separate
      registration and configuration calls, as seen in the test programs.
      model_net_set_params is no longer used, and is replaced by model_net_register
      and model_net_configure. The dragonfly network, having two LP types bundled in
      the same code-path, is special-cased in the registration code.
      LP-mapping in model-net now has the following defaults:
      - counts via codes_mapping_get_lp_count are now with respect to the calling
        network LP's annotation.
      - when looking up network LPs via
        codes_mapping_get_lp_info/codes_mapping_get_lp_id, the annotation of the
        calling network LP is used. Hence, routing now occurs only between LPs of the
        same annotation. If the destination LP's group specified by model_net_*event
        does not contain a modelnet LP with the same annotation as the modelnet LP in
        the sender's group, then an error will occur (in codes_mapping).
      Known Issues:
      - modelnet users currently cannot specify which modelnet LP to use in the case
        of multiple modelnet LPs in the sender's group. This will be fixed in future
        commits after a consensus is reached on the best way to expose this
  6. 18 Jul, 2014 1 commit
  7. 08 Jul, 2014 1 commit
    • Jonathan Jenkins's avatar
      configuration method change allowing multiple networks · 8ef0ddb7
      Jonathan Jenkins authored
      - "modelnet" parameter in cfg is now a no-op
      - "modelnet_order" parameter in cfg is required,
        listing order in which networks are indexed to
        the model
      - modified "model_net_set_params" signature
      - updated tests to use the new interface
  8. 30 Jun, 2014 1 commit
  9. 11 Jun, 2014 1 commit
  10. 21 May, 2014 1 commit
  11. 05 May, 2014 2 commits
  12. 10 Jan, 2014 1 commit
    • Philip Carns's avatar
      remove implicit lp io prepare and flush · 7217dbfe
      Philip Carns authored
      - 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
  13. 13 Oct, 2013 1 commit
  14. 29 Aug, 2013 1 commit
  15. 27 Aug, 2013 1 commit
  16. 09 Aug, 2013 1 commit
    • Misbah Mubarak's avatar
      Updates to modelnet (1) Updated the mapping configuration for dragonfly (the... · 7a4ef14f
      Misbah Mubarak authored
      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
  17. 08 Aug, 2013 1 commit
  18. 07 Aug, 2013 1 commit
  19. 05 Aug, 2013 2 commits
  20. 31 Jul, 2013 2 commits
  21. 30 Jul, 2013 1 commit