ahill/iproute2
1
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/iproute2/iproute2.git synced 2026-01-26 14:13:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

man: mptcp: 'backup' flag also affects outgoing data

Browse Source 
That's the behaviour with the default packet scheduler.

In some early design, the default scheduler was supposed to take into
account only the received backup flags, but it ended up not being the
case, and setting the flag would also affect outgoing data.

Suggested-by: Mat Martineau <martineau@kernel.org>
Acked-by: Mat Martineau <martineau@kernel.org>
Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
This commit is contained in:
Matthieu Baerts (NGI0) 2024-07-27 12:10:33 +02:00 committed by Stephen Hemminger
parent 8251786f3d
commit e3c1e2a4e2
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
man/man8/ip-mptcp.8
View File

@ -170,10 +170,12 @@ typically do this.
If this is a
.BR subflow
endpoint, the subflows created using this endpoint will have the backup
flag set during the connection process. This flag instructs the peer to
only send data on a given subflow when all non-backup subflows are
unavailable. This does not affect outgoing data, where subflow priority
is determined by the backup/non-backup flag received from the peer
flag set during the connection process. This flag instructs the remote
peer to only send data on a given subflow when all non-backup subflows
are unavailable. When using the default packet scheduler with a 'backup'
endpoint, outgoing data from the local peer is also affected: packets
will only be sent from this endpoint when all non-backup subflows are
unavailable.
.TP
.BR fullmesh