• Ilpo Jrvinen's avatar
    [TCP] FRTO: Use of existing funcs make code more obvious & robust · 3e6f049e
    Ilpo Jrvinen authored
    Though there's little need for everything that tcp_may_send_now
    does (actually, even the state had to be adjusted to pass some
    checks FRTO does not want to occur), it's more robust to let it
    make the decision if sending is allowed. State adjustments
    needed:
    - Make sure snd_cwnd limit is not hit in there
    - Disable nagle (if necessary) through the frto_counter == 2
    
    The result of check for frto_counter in argument to call for
    tcp_enter_frto_loss can just be open coded, therefore there
    isn't need to store the previous frto_counter past
    tcp_may_send_now.
    
    In addition, returns can then be combined.
    Signed-off-by: default avatarIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    3e6f049e
tcp_input.c 149 KB