GitLab maintenance scheduled for Tomorrow, 2020-03-31, from 17:00 to 18:00 CT - Services will be unavailable during this time.

  1. 04 Mar, 2015 1 commit
  2. 27 Feb, 2015 4 commits
  3. 25 Feb, 2015 2 commits
  4. 26 Jan, 2015 1 commit
  5. 16 Jan, 2015 1 commit
  6. 08 Jan, 2015 1 commit
  7. 05 Jan, 2015 1 commit
  8. 23 Dec, 2014 1 commit
  9. 22 Dec, 2014 1 commit
  10. 10 Dec, 2014 1 commit
  11. 13 Nov, 2014 1 commit
  12. 07 Nov, 2014 2 commits
  13. 06 Nov, 2014 4 commits
  14. 05 Nov, 2014 2 commits
  15. 04 Nov, 2014 3 commits
  16. 03 Nov, 2014 4 commits
  17. 09 Oct, 2014 2 commits
  18. 29 Aug, 2014 1 commit
  19. 21 Aug, 2014 1 commit
  20. 20 Aug, 2014 1 commit
    • Jonathan Jenkins's avatar
      recv-side queuing support (loggp only) · 6f9bc775
      Jonathan Jenkins authored
      Rather than model-net LPs directly sending messages to other model-net LPs, LPs
      can route the intended message through the scheduler interface to be queued up
      for reception by the receiver (see the diff of loggp.c). This has the benefit of
          enabling things like priority and fairness for N->1 communication patterns.
          Currently, no packetizing is supported, and I haven't yet wrote checks for
          it - beware.
      
      Loggp is currently the only supported model. simplenet could also be supported
      without much trouble, but I doubt there's any demand for it at the moment.  This
      should NOT be used by the dragonfly/torus models, as they have their own routing
      backend.
      6f9bc775
  21. 19 Aug, 2014 2 commits
  22. 18 Aug, 2014 1 commit
  23. 15 Aug, 2014 2 commits
    • Jonathan Jenkins's avatar
      scheduler fix for other networks (NOT torus, simplewan) · 0164aa2d
      Jonathan Jenkins authored
      Torus and simplewan each have problems precluding them from the current
      scheduling fix:
      - simplewan - each "device" has N input/output ports. It can't simply tell the
        scheduler when they are (it is?) idle because the scheduler doesn't know which
        packets go to which ports
      - torus - also has N input/output ports (two for each dimension). Also, the same
        routing "queue" (via the "next_link_available_time" var) is used for incoming
        and outgoing messages, so we can't guarantee the scheduler that we'll be
        available at time x (an incoming msg could arrive and then be routed at time
        x-1). This isn't a problem for the dragonfly network as terminals aren't
        intermediate routers. Ideally what needs to happen here is for the
        intermediate packets/chunks to be queued up in the scheduler.
      0164aa2d
    • Jonathan Jenkins's avatar
      scheduler - sched loop is callback-driven now (loggp only) · b3650ede
      Jonathan Jenkins authored
      - previously, packet issues were done without any consideration for device
        availability - within epsilon, preventing any meaningful scheduling
      - enabled for loggp only, other networks will be incorporated shortly
      b3650ede