From: Jason Baron <[email protected]> Date: Thu, 14 Jul 2016 11:38:40 -0400
> From: Jason Baron <[email protected]> > > The per-socket rate limit for 'challenge acks' was introduced in the > context of limiting ack loops: > > commit f2b2c582e824 ("tcp: mitigate ACK loops for connections as tcp_sock") > > And I think it can be extended to rate limit all 'challenge acks' on a > per-socket basis. > > Since we have the global tcp_challenge_ack_limit, this patch allows for > tcp_challenge_ack_limit to be set to a large value and effectively rely on > the per-socket limit, or set tcp_challenge_ack_limit to a lower value and > still prevents a single connections from consuming the entire challenge ack > quota. > > It further moves in the direction of eliminating the global limit at some > point, as Eric Dumazet has suggested. This a follow-up to: > Subject: tcp: make challenge acks less predictable > > Cc: Eric Dumazet <[email protected]> > Cc: David S. Miller <[email protected]> > Cc: Neal Cardwell <[email protected]> > Cc: Yuchung Cheng <[email protected]> > Cc: Yue Cao <[email protected]> > Signed-off-by: Jason Baron <[email protected]> Applied, thanks.
