Open matttbe opened 1 year ago
How about invoking __mptcp_push_pending() right after mptcp_pm_nl_work() in mptcp_worker(). Something like:
mptcp_pm_nl_work(msk);
+ __mptcp_push_pending(sk, 0);
+
mptcp_check_send_data_fin(sk);
mptcp_check_data_fin_ack(sk);
mptcp_check_data_fin(sk);
How about invoking __mptcp_push_pending() right after mptcp_pm_nl_work() in mptcp_worker().
I forgot to reply to this one: we talked about that suggestion at the weekly meeting on the 19th of Sept
It doesn't seem OK:
From the last meeting:
What is important before sending any changes to netdev, is to have a "performance environment":
It looks like this work on the scheduler is challenging, and it would be better to prepare this work, split it, etc.:
When discussing about the packet scheduler API at the last meeting, it sounds very likely the current packet scheduler will not react by queuing more packets if some subflows only events are emitted, e.g. new TCP ACKs are received only acking things at TCP-level but not at MPTCP level.
The scheduler should probably be called when such events happen.
This can be checked with packetdrill: a ACK is received at TCP level and the scheduler might not send anything while it should (there is more room available).
Hints: