-
-
Notifications
You must be signed in to change notification settings - Fork 44
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tg import create t/mptcp-do-not-block-subflows-creation-on-errors
- Loading branch information
Showing
1 changed file
with
22 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,23 @@ | ||
From: Matthieu Baerts <matthieu.baerts@tessares.net> | ||
Subject: [PATCH] t/mptcp-do-not-block-subflows-creation-on-errors | ||
From: Paolo Abeni <pabeni@redhat.com> | ||
Subject: [PATCH] mptcp: do not block subflows creation on errors | ||
|
||
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net> | ||
If the MPTCP configuration allows for multiple subflows | ||
creation, and the first additional subflows never reach | ||
the fully established status - e.g. due to packets drop or | ||
reset - the in kernel path manager do not move to the | ||
next subflow. | ||
|
||
This patch introduces a new PM helper to cope with MPJ | ||
subflow creation failure and delay and hook it where appropriate. | ||
|
||
Such helper triggers additional subflow creation, as needed | ||
and updates the PM subflow counter, if the current one is | ||
closing. | ||
|
||
Additionally start all the needed additional subflows | ||
as soon as the MPTCP socket is fully established, so we don't | ||
have to cope with slow MPJ handshake blocking the next subflow | ||
creation. | ||
|
||
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com> | ||
Signed-off-by: Paolo Abeni <pabeni@redhat.com> |