User Tools

Site Tools


midd:traffic_scheduling:project_log

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
midd:traffic_scheduling:project_log [2009/04/25 00:54]
perryk
midd:traffic_scheduling:project_log [2009/04/28 22:57]
perryk
Line 205: Line 205:
  
 {{:​midd:​traffic_scheduling:​server_snap.jpg|}} {{:​midd:​traffic_scheduling:​server_snap.jpg|}}
 +
 +==== 04/25 ====
 +
 +PK - Decided to take a chance to write super-TCP. Came up with plan. Spent 24 hours straight on it. Concluded it is too big for this late in the semester.
 +
 +==== 04/27 ====
 +
 +PK - AB - several hour meeting came up with concrete plan for finishing this project. ​
 +
 +PK - started over again. ​
 +
 +==== 04/28 ====
 +
 +PK - experimented with blocking and non-blocking socket member. With non-blocking I crashed my computer every time when I hammered the adapter but did not do this with blocking set. Flag must do something :). Later this day: First fully functioning version of new client / server. ​
 +
 +PK - AB - meet for an hour for code review, status. ​
 +
 +PK - a few more hours in. I added three more transmission "​models"​ to the client: load,burst and random. I have replaced the processor based clock and am now using DateTime.Now.Ticks to make the code portable to Linux. This means same-machine/​same-subnet RTTs are 0. I added the adapter cumulative loss/ooo counts. I added timestamps in acks. Have conclusive evidence that the blocking socket flag does nothing in UDP. Forced to put in Thread.SpinWait every N bulk transmissions so that we don't spill so many segments on the floor, even before they'​ve hit the wire.
 +
 +
  
midd/traffic_scheduling/project_log.txt ยท Last modified: 2009/05/15 14:55 by afbarnard