MPTCP Linux Development
 help / color / mirror / Atom feed
From: Geliang Tang <geliangtang@gmail.com>
To: mptcp@lists.linux.dev, geliangtang@gmail.com
Cc: Geliang Tang <geliangtang@xiaomi.com>
Subject: [MPTCP][PATCH v6 mptcp-next 0/5] fullmesh path manager support
Date: Tue, 27 Jul 2021 21:24:28 +0800	[thread overview]
Message-ID: <cover.1627391588.git.geliangtang@xiaomi.com> (raw)

From: Geliang Tang <geliangtang@xiaomi.com>

v6:
 - drop lookup_subflow_by_addrs()
 - pass three arrays instead of 'entries' in fill_local_adresses_vec()
 - drop the 'remote' argument of fill_local_addresses_vec
 - drop the 'local' argument of fill_remote_addresses_vec
 - fix the pm.subflows.
 - add limit testcase.

v5:
 - patch 1, add a new helper lookup_address_in_vec.
 - patch 2, update pm.subflows in the non-fullmesh case.
 - patch 4, add more tests.
 - tag: export/20210727T054640

v4:
 - add new helpers, fill_local/remote_addresses_vec
 - add max_subflows checks
 - add 'local' into the local addresses array only when no fullmesh
   entry found.
 - add signal,fullmesh check

v3:
 - the in-kernel fullmesh path manager has been dropped from this
   patchset, only keep the fullmesh flag support code.

v2:
 - Implement the fullmesh mode as an extension to the netlink PM, not a
   standalone PM as Paolo suggested.
 - drop duplicate code.
 - add a new per endpoint flag MPTCP_PM_ADDR_FLAG_FULLMESH.

Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/193

Geliang Tang (5):
  mptcp: remote addresses fullmesh
  mptcp: local addresses fullmesh
  selftests: mptcp: set and print the fullmesh flag
  selftests: mptcp: add fullmesh testcases
  selftests: mptcp: delete uncontinuous removing ids

 include/uapi/linux/mptcp.h                    |   1 +
 net/mptcp/pm_netlink.c                        | 145 ++++++++++++++++--
 .../testing/selftests/net/mptcp/mptcp_join.sh |  67 +++++++-
 tools/testing/selftests/net/mptcp/pm_nl_ctl.c |  16 +-
 4 files changed, 206 insertions(+), 23 deletions(-)

-- 
2.31.1


             reply	other threads:[~2021-07-27 13:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 13:24 Geliang Tang [this message]
2021-07-27 13:24 ` [MPTCP][PATCH v6 mptcp-next 1/5] mptcp: remote addresses fullmesh Geliang Tang
2021-07-27 13:24   ` [MPTCP][PATCH v6 mptcp-next 2/5] mptcp: local " Geliang Tang
2021-07-27 13:24     ` [MPTCP][PATCH v6 mptcp-next 3/5] selftests: mptcp: set and print the fullmesh flag Geliang Tang
2021-07-27 13:24       ` [MPTCP][PATCH v6 mptcp-next 4/5] selftests: mptcp: add fullmesh testcases Geliang Tang
2021-07-27 13:24         ` [MPTCP][PATCH v6 mptcp-next 5/5] selftests: mptcp: delete uncontinuous removing ids Geliang Tang
2021-07-28 17:21         ` [MPTCP][PATCH v6 mptcp-next 4/5] selftests: mptcp: add fullmesh testcases Paolo Abeni
2021-07-28 17:41           ` Matthieu Baerts
2021-07-29  7:09             ` Geliang Tang
2021-07-28 17:22 ` [MPTCP][PATCH v6 mptcp-next 0/5] fullmesh path manager support Paolo Abeni
2021-07-29  0:17 ` Mat Martineau

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1627391588.git.geliangtang@xiaomi.com \
    --to=geliangtang@gmail.com \
    --cc=geliangtang@xiaomi.com \
    --cc=mptcp@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox