The core is currently marking a subflow as "stale" after a certain number of losses (net.mptcp.stale_loss_cnt).
A packet scheduler might be able to do the same for other reasons: e.g. if a subflow is considered as "really bad" by the scheduler (e.g. too high latency, too unstable, etc.) and it should not be used for the moment, the scheduler will want to mark the subflow as "stale" and have a regular probing (linked to #348).
The packet scheduler should either:
Because the "stale" bit is tightly linked to the RTO (a subflow will no longer be considered as "stale" by the core and unmarked when a packet has been acked on this subflow), it should because to manage a new bit where only the packet scheduler will be able to mark and unmark it as "temporarily unusable" ("skip this subflow if possible").
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4