> From: Paolo Abeni <[email protected]>
> 
> Currently the MPTCP core enforces that when MPTCP-level retrans timer
> fires, at most a single dfrag is retransmitted. In some corner-cases, it
> may be necessary to retransmit multiple dfrags, and the MPTCP socket
> will need to wait multiple retrans timeout to accomplish that.
> 
> Remove the mentioned constraint, allowing to transmit multiple dfrags
> per retrans period, as long as the scheduler keeps selecting subflows
> for retransmissions and pending data is available in the rtx queue.
> The default scheduler will transmit a dfrag per available subflow.
> 
> Tested-by: Gang Yan <[email protected]>
> Tested-by: Geliang Tang <[email protected]>
> Acked-by: Geliang Tang <[email protected]>
> Signed-off-by: Paolo Abeni <[email protected]>
> Signed-off-by: Matthieu Baerts (NGI0) <[email protected]>
> Link: 
> https://patch.msgid.link/20260807-net-next-mptcp-oooq-pruning-v3-3-dbc1eb853...@kernel.org
> Signed-off-by: Jakub Kicinski <[email protected]>
> (cherry picked from commit 96d846e3e2a7ea01ff8a584a0b5e2a42fa9ccc1e)
> 
> https://virtuozzo.atlassian.net/browse/VSTOR-153491
> Feature: fix ms/net
> Signed-off-by: Eva Kurchatova <[email protected]>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review ยท 
https://sashiko.vzint.dev/#/patchset/[email protected]?part=4


_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel

Reply via email to