1. 17 Feb, 2007 1 commit
  2. 16 Feb, 2007 2 commits
  3. 15 Feb, 2007 1 commit
  4. 14 Feb, 2007 5 commits
  5. 13 Feb, 2007 3 commits
  6. 12 Feb, 2007 1 commit
  7. 07 Feb, 2007 1 commit
  8. 06 Feb, 2007 1 commit
  9. 13 Dec, 2006 1 commit
  10. 01 Dec, 2006 1 commit
  11. 08 Oct, 2006 1 commit
  12. 06 Oct, 2006 1 commit
  13. 03 Oct, 2006 2 commits
  14. 28 Sep, 2006 1 commit
  15. 22 Sep, 2006 1 commit
  16. 19 Sep, 2006 2 commits
  17. 18 Sep, 2006 1 commit
    • Kirk Webb's avatar
      · a290c985
      Kirk Webb authored
      Modify the monitor to use the event system directly via the python SWIG
      wrapper object (requested by Rob).  The monitor no longer forks and execs
      tevc for set_link operations.  Tested the additional code here by transplanting
      it into a test script.  Works as expected there, but has not been tested
      in situ.
  18. 14 Sep, 2006 1 commit
    • Jonathon Duerig's avatar
      Added better monitoring of replay save/load format. Changed census function to... · ee9ee12f
      Jonathon Duerig authored
      Added better monitoring of replay save/load format. Changed census function to reduce the possibility of future size errors. New monitoring is hierarchical and should be essentially free as long as the #define in saveload.cc is commented out. Added LeastSquaresThroughput to the sensorlist and the definitions in monitor.py. A couple of miscellaneous fixes.
  19. 01 Sep, 2006 3 commits
  20. 29 Aug, 2006 1 commit
    • Mike Hibler's avatar
      Revised version of "max delay" packet dropping in dummynet. · f0b988f1
      Mike Hibler authored
       * Delay specified in ticks.
       * Drop performed as packets were leaving the delay queue (i.e., leaving
         dummynet).  This is more accurate in terms of calculating time spent
         in dummynet, and can be used with all strategies of BW/delay shaping
         (constant values, distributions, table lookup), but required that
         ultimately-dropped packets get put on the BW queue, changing the timing
         of things.
       * Delay specified in milliseconds.
       * Drops perfromed as packets enter the bandwidth queue (i.e., arrive
         in dummynet).  Here drops are based on estimates of how long a packet
         would spend in dummynet and thus only works with constant delay/BW
         shaping characteristics, but does more accurately reflect queuing
      The estimate is done by looking at the length in bytes of the bandwidth
      queue (including the candidate packet) for the pipe, determining how long
      it will take to transmit that many bytes, and then adding the delay value
      for the pipe.
  21. 25 Aug, 2006 1 commit
  22. 24 Aug, 2006 1 commit
    • Jonathon Duerig's avatar
      Fixed the traffic model so that it is now in line with what Rob and I... · c6fa578a
      Jonathon Duerig authored
      Fixed the traffic model so that it is now in line with what Rob and I discussed. Delays are before the write with the write size cached. Writes expire based on an expiration date.
      Miscellaneous fixes. Open problem: PacketSensor does not deal correctly with zero-sized packets. I changed KernelTcp to pass such packets because otherwise there is no way to do state changes based on SYN/FIN/other packets. SYN is handled ok for now because of a change noted below. FIN is not.
      Added a StateSensor. As I discovered, using the kernel tcp_info data structure isn't useful when dealing with fields that change on a packet by packet basis because the kernel information is retrieved at processing time and not capture time. For instance, it is useless when trying to determine whether a connection was established by the time a particular packet was sent (to determine whether it is part of the three-way-handshake). The StateSensor keeps track of the state machine and correlates it to the packet involved. This allows the other sensors to rely on it to distinguish between connection setup and the rest of the connection traffic. Added references to it in the PacketSensor, the DelaySensor and the ThroughputSensor.
      Changed the way packet information was transmitted to the sensors to make it easier to add new packet types (as will be necessary when accept()s are handled).
      Fixed all outstanding flaws in the basic feedback mechanism. In short, "Its alive!". Currently the only data being transmitted is the base rtt (MinDelay). Now that the feedback is working in a basic form, it will be easier to get the other characteristics online.
  23. 18 Aug, 2006 1 commit
  24. 11 Aug, 2006 1 commit
  25. 01 Jun, 2006 1 commit
  26. 24 Apr, 2006 1 commit
  27. 11 Apr, 2006 2 commits
  28. 06 Apr, 2006 1 commit