Lines Matching defs:reordering
440 nr_segs = max_t(u32, nr_segs, tp->reordering + 1);
1030 * DSACKs that may have been due to reordering causing RACK to trigger
1032 * without having seen reordering, or that match TLP probes (TLP
1045 /* It's reordering when higher sequence was delivered (i.e. sacked) before
1046 * some lower never-retransmitted sequence ("low_seq"). The maximum reordering
1047 * distance is approximated in full-mss packet distance ("reordering").
1061 if ((metric > tp->reordering * mss) && mss) {
1065 tp->reordering,
1070 tp->reordering = min_t(u32, (metric + mss - 1) / mss,
1174 * ever retransmitted -> reordering. Alas, we cannot use it
1177 * for retransmitted and already SACKed segment -> reordering..
1224 * fragmentation and packet reordering past skb's retransmission. To consider
1400 * which was in hole. It is reordering.
1880 /* Don't count olds caused by ACK reordering */
2039 * in assumption of absent reordering, interpret this as reordering.
2049 tp->reordering = min_t(u32, tp->packets_out + addend,
2160 u8 reordering;
2179 * suggests that the degree of reordering is over-estimated.
2181 reordering = READ_ONCE(net->ipv4.sysctl_tcp_reordering);
2183 tp->sacked_out >= reordering)
2184 tp->reordering = min_t(unsigned int, tp->reordering,
2185 reordering);
2230 * With reordering, holes may still be in flight, so RFC3517 recovery
2297 * (reordering). This is implemented in tcp_mark_head_lost and
2326 * fast retransmit (reordering) and underestimated RTO, analyzing
2348 if (!tcp_is_rack(sk) && tcp_dupack_heuristics(tp) > tp->reordering)
2356 * has at least tp->reordering SACKed seqments above it; "packets" refers to
2410 int sacked_upto = tp->sacked_out - tp->reordering;
2903 tp->snd_una + tp->reordering * tp->mss_cache);
2914 * packet, rather than with a retransmit. Check reordering.
2918 /* We are getting evidence that the reordering degree is higher
3039 * starts a new recovery (e.g. reordering then loss);
3410 /* Non-retransmitted hole got filled? That's reordering */
3495 /* If reordering is high then always grow cwnd whenever data is
3501 if (tcp_sk(sk)->reordering >
4285 * the biggest problem on large power networks even with minor reordering.