RF Pipe tx datarate not enforced under certain load conditions #40
Assignees
Labels
Comments
|
This bug affects the develop branch. |
sgalgano
added a commit
that referenced
this issue
Dec 4, 2015
downstream traffic arrives it is possible for the packet queue to be empty but the previous packet end-of-transmission (EOT) time to still be in the future. Failure to check for that condition leads to immediate transmission of the newly arrived packet instead of waiting for EOT. Additional code was added to processDownstreamPacket() to test for a currentEndOfTransmissionTime_ in the future in order to determine if a callback should be scheduled or if the newly arrived packet can be immediately sent. Additional code was added to handleDownstreamQueueEntry() to engage transmission logic even if the scheduled handler had been short circuited as long as there exists a packet to transmit in the queue and currentEndOfTransmissionTime_ has past. Configurable jitter and fixed delay logic was modified to apply the values when figuring out currentEndOfTransmissionTime_ for the purposes of determining the earliest possible time another packet may be transmitted. See #40
Merged
|
See #42 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Under high traffic load and certain data rate configurations, when down stream traffic arrives it is possible for the packet queue to be empty but the previous packet end-of-transmission (EOT) time to still be in the future. Failure to check for that condition leads to immediate transmission of the newly arrived packet instead of waiting for EOT.
Found during regression testing and re-verified with iperf.
The text was updated successfully, but these errors were encountered: