Closed yverbin closed 5 years ago
Hello @yverbin,
did you already test the default scheduler and does this also happen with it? Do you have any further hints how to reproduce this?
Hello @s6dlwebe. It looks like that all is fine with default scheduler but i dont have enough statistics. Several tests have been passed successfully until cases with modems and blest scheduler
@s6dlwebe :
/* is the required space available in the mptcp meta send window?
* we assume that all bytes inflight on the slow path will be acked in besttp->srtt seconds
* (just like the SKB if it was sent now) -> that means that those inflight bytes will
* keep occupying space in the meta window until then
*/
slow_inflight_bytes = besttp->write_seq - besttp->snd_una;
slow_bytes = skb->len + slow_inflight_bytes; // bytes of this SKB plus those in flight already
skb
can be NULL (see the callers of blest_get_available_subflow()
.
good catch! Thank you for your quick reference to the problem.
Today I will find some time and provide a patch for this bug.
I also have to do some other minor maintenance (adding mptcp_retransmit
tracepoint and penalizing all subflows) on BLEST anyway. Seems like @matttbe hasn't committed my patch-set yet and I had some problems getting git-sendmail configuration to work on my new machine. I will just resent both later to the mailing list or do you prefer a PR for this bugfix?
Seems like @matttbe hasn't committed my patch-set yet and I had some problems getting git-sendmail configuration to work on my new machine. I will just resent both later to the mailing list or do you prefer a PR for this bugfix?
Sorry I might have missed something. Are you talking about #351 ?
Sorry I might have missed something. Are you talking about #351 ?
No problem - I was the one who did not follow your workflow, so I am sorry. I sent the two patches directly to you instead to the mailing list because I did had some trouble getting git-sendemail to work on my machine. But I will just send them again later today with this bugfix.
No, I was not talking about #351. That will take me some extra time to include your feedback.
I have collected statistics and modems do not affect the problem. With default scheduler all works fine
I have collected statistics and modems do not affect the problem. With default scheduler all works fine
Thank you @yverbin for reporting and investigating the problem with us 👍 . Although BLEST and the default scheduler have a lot in common, this bug is indeed only related to BLEST as @cpaasch has already spotted 🥇 the problem in the part that does the blocking estimation.
I compiled a kernel from commit https://github.com/s6dlwebe/mptcp/commit/66efd0e8534a2f8f737cff4234c5d9d00096d86c. At first glance this problem is solved 👍
In my opinion, the problem occurs when usb modems are connected to pc.