diff options
| author | Paolo Abeni <pabeni@redhat.com> | 2023-06-20 18:30:17 +0200 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2023-06-21 22:45:57 -0700 |
| commit | 6f06b4d4d1cc676a3f9d947f931ec3866b6c4f6c (patch) | |
| tree | f1161c9ff3e94371b542f929e70b61d23350dc74 /net/unix/af_unix.c | |
| parent | 5dcff89e14555a4ee6cfa132b82f7d13dcb1e80a (diff) | |
| download | linux-6f06b4d4d1cc676a3f9d947f931ec3866b6c4f6c.tar.gz linux-6f06b4d4d1cc676a3f9d947f931ec3866b6c4f6c.tar.bz2 linux-6f06b4d4d1cc676a3f9d947f931ec3866b6c4f6c.zip | |
mptcp: add subflow unique id
The user-space need to properly account the data received/sent by
individual subflows. When additional subflows are created and/or
closed during the MPTCP socket lifetime, the information currently
exposed via MPTCP_TCPINFO are not enough: subflows are identified only
by the sequential position inside the info dumps, and that will change
with the above mentioned events.
To solve the above problem, this patch introduces a new subflow
identifier that is unique inside the given MPTCP socket scope.
The initial subflow get the id 1 and the other subflows get incremental
values at join time.
Link: https://github.com/multipath-tcp/mptcp_net-next/issues/388
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Reviewed-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Matthieu Baerts <matthieu.baerts@tessares.net>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions