Skip to content
Snippets Groups Projects
  1. Jan 30, 2019
  2. Jan 16, 2019
  3. Jan 14, 2019
  4. Jan 09, 2019
  5. Jan 08, 2019
  6. Dec 28, 2018
  7. Dec 27, 2018
  8. Dec 24, 2018
  9. Dec 20, 2018
  10. Nov 29, 2018
  11. Nov 28, 2018
  12. Nov 27, 2018
  13. Nov 25, 2018
  14. Nov 20, 2018
  15. Nov 16, 2018
  16. Nov 15, 2018
    • Aastha Mehta's avatar
      bugfixes: storing cwnd prior to loss or recovery state for subsequent... · b25a16bf
      Aastha Mehta authored
      bugfixes: storing cwnd prior to loss or recovery state for subsequent restoration under undo_cwnd_reduction
      
      (1) in ptcp_enter_loss, store prior cwnd value only if entering loss the
      first time. if entering loss (CA 4) from recovery or CWR state, copy the
      prior_cwnd into loss_prior_cwnd.
      (2) during undo_cwnd_reduction, restore to loss_prior_cwnd if state is
      Loss, otherwise restore to prior_cwnd.
      b25a16bf
    • Aastha Mehta's avatar
      revert redundant commit 307afdc2 · dc6d4504
      Aastha Mehta authored
      avoid coalescing by setting net.ipv4.tcp_retrans_collapse = 0
      dc6d4504
  17. Nov 14, 2018
    • Aastha Mehta's avatar
      rewrite ptcp_enter_loss · 96a73c84
      Aastha Mehta authored
      (1) first retract cwnd and hypace cwm
      (2) then sync packet counts
      (3) then mark packets upto packet_count as lost
      this has a small problem where a packet unsent in tcp with lower seq# is
      marked lost, whereas a dummy with a higher seq# that was actually sent
      must be treated as not lost. potentially it looks as if there were
      losses in the middle of a stream but subsequent packets were transmitted
      even before recovering from the intermediate losses.
      96a73c84
  18. Nov 13, 2018
  19. Nov 12, 2018
  20. Nov 11, 2018
  21. Nov 06, 2018
  22. Oct 04, 2018
  23. Oct 03, 2018
  24. Oct 01, 2018
  25. Sep 30, 2018
Loading