Searched refs:undo_marker (Results 1 – 4 of 4) sorted by relevance
1106 tp->undo_marker ? tp->undo_retrans : 0); in tcp_check_sack_reordering() 1246 * SND.UNA down to undo_marker, which is the last point of interest. Yet1250 * fully below undo_marker they do not affect behavior in anyway and can1275 if (!is_dsack || !tp->undo_marker) in tcp_is_sackblock_valid() 1282 if (!before(start_seq, tp->undo_marker)) in tcp_is_sackblock_valid() 1286 if (!after(end_seq, tp->undo_marker)) in tcp_is_sackblock_valid() 1290 * start_seq < undo_marker and end_seq >= undo_marker. in tcp_is_sackblock_valid() 1326 if (tp->undo_marker && tp->undo_retrans > 0 && in tcp_check_dsack() 1328 after(end_seq_0, tp->undo_marker)) in tcp_check_dsack() [all...]
603 newtp->undo_marker = treq->snt_isn; in tcp_create_openreq_child()
427 u32 undo_marker; /* snd_una upon a new recovery episode. */ member
712 updated. Which counter will be updated depends on the undo_marker flag713 of the TCP socket. If the undo_marker is not set, the TCP stack isn't717 will be updated. If the undo_marker is set, TcpExtTCPDSACKIgnoredOld