Mat Martineau <mathew.j.martineau(a)linux.intel.com> wrote:
We can still get inconsistent retransmission behavior depending on
of subflows in the list - if the first non-loss subflow has an empty write
queue then retransmission will happen even if other subflows have queued
data. I suppose this causes the opposite problem, retransmitting when it
should wait. Better to handle a fix for that separately?
Yes, if we observe too many bogus retransmits then the mptcp-level
retransmit timer is firing too early, i'd say thats a different bug.