Repurposed the pktRcvAvgBelatedTime to trace the unique packet delay. #2540
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed statistics related to
pktRcvAvgBelatedTime
andpktRcvBelated
.pktRcvAvgBelatedTime
has changed the purpose, as previous one was useless and meaningless, while the new meaining partially matches the name. This means now: the average distance between ETS and arrival time. ETS is the expected arrival time which is identical to arrival time for the very first data packet and as the calculation of the TsbPdTime currently involves the latency setting, this time is calculated basing on the TsbPdTime by decreasing it by latency, that is, it's the time when particular packet, stating by its timestamp, would arrive if the network traveling time was identical to the one of the very first data packet. This value can be used in trial transmissions to have idea how much on average the packet could be delayed in the network more than expected, as this value eats up time reserved by latency. This will be helpful in better shaping the latency settings to avoid dropped packets due to too little time reserved for retransmission. Note that this stat doesn't trace the extra time eaten up by retransmitted packets (for that purpose additional stats can be added).pktRcvBelated
that calculates packets that were rejected due to being received too late, was doing it a bit incorrectly. This is now calculated for every packet that has a sequence number in the past for the buffer. This still doesn't state whether a packet was received useful (that is, if this isn't a duplicated packet that was retransmitted uselessly).