1. 26 Aug, 2007 1 commit
  2. 02 Aug, 2007 2 commits
  3. 31 Jul, 2007 3 commits
    • Ilpo Järvinen's avatar
      [TCP]: Bidir flow must not disregard SACK blocks for lost marking · b8ed601c
      Ilpo Järvinen authored
      It's possible that new SACK blocks that should trigger new LOST
      markings arrive with new data (which previously made is_dupack
      false). In addition, I think this fixes a case where we get
      a cumulative ACK with enough SACK blocks to trigger the fast
      recovery (is_dupack would be false there too).
      I'm not completely pleased with this solution because readability
      of the code is somewhat questionable as 'is_dupack' in SACK case
      is no longer about dupacks only but would mean something like
      'lost_marker_work_todo' too... But because of Eifel stuff done
      in CA_Recovery, the FLAG_DATA_SACKED check cannot be placed to
      the if statement which seems attractive solution. Nevertheless,
      I didn't like adding another variable just for that either... :-)
      Signed-off-by: default avatarIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Ilpo Järvinen's avatar
      [TCP]: Fix ratehalving with bidirectional flows · 1e757f99
      Ilpo Järvinen authored
      Actually, the ratehalving seems to work too well, as cwnd is
      reduced on every second ACK even though the packets in flight
      remains unchanged. Recoveries in a bidirectional flows suffer
      quite badly because of this, both NewReno and SACK are affected.
      After this patch, rate halving is performed for ACK only if
      packets in flight was supposedly changed too.
      Signed-off-by: default avatarIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    • Stephen Hemminger's avatar
      [TCP]: congestion control API pass RTT in microseconds · 30cfd0ba
      Stephen Hemminger authored
      This patch changes the API for the callback that is done after an ACK is
      received. It solves a couple of issues:
        * Some congestion controls want higher resolution value of RTT
          (controlled by TCP_CONG_RTT_SAMPLE flag). These don't really want a ktime, but
          all compute a RTT in microseconds.
        * Other congestion control could use RTT at jiffies resolution.
      To keep API consistent the units should be the same for both cases, just the
      resolution should change.
      Signed-off-by: default avatarStephen Hemminger <shemminger@linux-foundation.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  4. 18 Jul, 2007 1 commit
  5. 15 Jul, 2007 1 commit
  6. 15 Jun, 2007 2 commits
  7. 14 Jun, 2007 1 commit
  8. 12 Jun, 2007 1 commit
  9. 03 Jun, 2007 1 commit
  10. 19 May, 2007 2 commits
  11. 30 Apr, 2007 2 commits
  12. 25 Apr, 2007 23 commits