From: Marcelo Ricardo Leitner > Sent: 29 March 2016 14:42 > > Currently on high rate SCTP streams the heartbeat timer refresh can > consume quite a lot of resources as timer updates are costly and it > contains a random factor, which a) is also costly and b) invalidates > mod_timer() optimization for not editing a timer to the same value. > It may even cause the timer to be slightly advanced, for no good reason. Interesting thoughts: 1) Is it necessary to use a different 'random factor' until the timer actually expires? 2) It might be better to allow the heartbeat timer to expire, on expiry work out the new interval based on when the last 'refresh' was done. David -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
