[TCP]: Add highest_sack seqno, points to globally highest SACK
It is guaranteed to be valid only when !tp->sacked_out. In most cases this seqno is available in the last ACK but there is no guarantee for that. The new fast recovery loss marking algorithm needs this as entry point. Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
d961db358f
commit
d738cd8fca
@ -333,6 +333,8 @@ struct tcp_sock {
|
||||
|
||||
struct tcp_sack_block_wire recv_sack_cache[4];
|
||||
|
||||
u32 highest_sack; /* Start seq of globally highest revd SACK (valid only in slowpath) */
|
||||
|
||||
/* from STCP, retrans queue hinting */
|
||||
struct sk_buff* lost_skb_hint;
|
||||
|
||||
|
Reference in New Issue
Block a user