1. 24 Sep, 2012 1 commit
    • Eric Eide's avatar
      Replace license symbols with {{{ }}}-enclosed license blocks. · 6df609a9
      Eric Eide authored
      This commit is intended to makes the license status of Emulab and
      ProtoGENI source files more clear.  It replaces license symbols like
      "EMULAB-COPYRIGHT" and "GENIPUBLIC-COPYRIGHT" with {{{ }}}-delimited
      blocks that contain actual license statements.
      
      This change was driven by the fact that today, most people acquire and
      track Emulab and ProtoGENI sources via git.
      
      Before the Emulab source code was kept in git, the Flux Research Group
      at the University of Utah would roll distributions by making tar
      files.  As part of that process, the Flux Group would replace the
      license symbols in the source files with actual license statements.
      
      When the Flux Group moved to git, people outside of the group started
      to see the source files with the "unexpanded" symbols.  This meant
      that people acquired source files without actual license statements in
      them.  All the relevant files had Utah *copyright* statements in them,
      but without the expanded *license* statements, the licensing status of
      the source files was unclear.
      
      This commit is intended to clear up that confusion.
      
      Most Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the Affero GNU General Public License, version 3
      (AGPLv3).
      
      Most Utah-copyrighted files related to ProtoGENI are distributed under
      the terms of the GENI Public License, which is a BSD-like open-source
      license.
      
      Some Utah-copyrighted files in the Emulab source tree are distributed
      under the terms of the GNU Lesser General Public License, version 2.1
      (LGPL).
      6df609a9
  2. 17 Feb, 2007 1 commit
  3. 16 Feb, 2007 2 commits
  4. 15 Feb, 2007 1 commit
  5. 14 Feb, 2007 5 commits
  6. 13 Feb, 2007 3 commits
  7. 12 Feb, 2007 1 commit
  8. 07 Feb, 2007 1 commit
  9. 06 Feb, 2007 1 commit
  10. 13 Dec, 2006 1 commit
  11. 01 Dec, 2006 1 commit
  12. 08 Oct, 2006 1 commit
  13. 06 Oct, 2006 1 commit
  14. 03 Oct, 2006 2 commits
  15. 28 Sep, 2006 1 commit
  16. 22 Sep, 2006 1 commit
  17. 19 Sep, 2006 2 commits
  18. 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.
      a290c985
  19. 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.
      ee9ee12f
  20. 01 Sep, 2006 3 commits
  21. 29 Aug, 2006 1 commit
    • Mike Hibler's avatar
      Revised version of "max delay" packet dropping in dummynet. · f0b988f1
      Mike Hibler authored
      OLD:
      
       * 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.
      
      NEW:
      
       * 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
         behavior.
      
      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.
      f0b988f1
  22. 25 Aug, 2006 1 commit
  23. 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.
      c6fa578a
  24. 18 Aug, 2006 1 commit
  25. 11 Aug, 2006 1 commit
  26. 01 Jun, 2006 1 commit
  27. 24 Apr, 2006 1 commit
  28. 11 Apr, 2006 2 commits