All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <tanggeliang@kylinos.cn>
Subject: [PATCH mptcp-next v6 0/5] BPF path manager, part 6
Date: Fri, 28 Mar 2025 12:01:30 +0800	[thread overview]
Message-ID: <cover.1743133948.git.tanggeliang@kylinos.cn> (raw)

From: Geliang Tang <tanggeliang@kylinos.cn>

v6:
 - squash accept_new_subflow patches into one.
 - change "pm->subflows == subflows_max - 1" to
	pm->subflows + 1 == subflows_max.
 - not to call accept_new_subflow under the PM lock.
 - add mptcp_pm_accept_subflow helpers.
 - drop READ_ONCE in mptcp_pm_worker.
 - clear all the pm status flags once in mptcp_pm_worker.

v5:
 - add comment "call from the subflow/msk context" for mptcp_sched_ops.
 - add new helper mptcp_pm_accept_new_subflow.
 - add "bool allow" parameter for mptcp_pm_accept_new_subflow, and drop
   .allow_new_subflow interface.
 - use a copy of pm->status in mptcp_pm_worker.
 - rename mptcp_pm_create_subflow_or_signal_addr with "__" prefix.
 - drop "!update_subflows" in mptcp_pm_subflow_check_next.
 - add_addr_received/rm_addr_received interfaces will be added in the
   next series.

v4:
 - address Matt's comments in v3. 
 - update pm locks in mptcp_pm_worker.
 - move the lock inside mptcp_pm_create_subflow_or_signal_addr.
 - move the lock inside mptcp_pm_nl_add_addr_received.
 - invoke add_addr_received interface from mptcp_pm_worker.
 - invoke rm_addr_received interface from mptcp_pm_rm_addr_or_subflow.
 - simply call mptcp_pm_close_subflow() in mptcp_pm_subflow_check_next.
 - https://patchwork.kernel.org/project/mptcp/cover/cover.1742804266.git.tanggeliang@kylinos.cn/

v3:
 - merge 'bugfixes for "BPF path manager, part 6, v2"' into this set.
 - https://patchwork.kernel.org/project/mptcp/cover/cover.1742521397.git.tanggeliang@kylinos.cn/

v2:
 - address Matt's comments in v1. 
 - add add_addr_received and rm_addr_received interfaces.
 - drop subflow_check_next interface.
 - add a "required" or "optional" comment for a group of interfaces in
   struct mptcp_pm_ops.

v1:
- https://patchwork.kernel.org/project/mptcp/cover/cover.1741685260.git.tanggeliang@kylinos.cn/

New interfaces for struct mptcp_pm_ops.

Geliang Tang (5):
  mptcp: pm: call pm worker handler without pm lock
  mptcp: pm: add accept_new_subflow() interface
  mptcp: pm: add established() interface
  mptcp: pm: add subflow_established() interface
  mptcp: pm: drop is_userspace in subflow_check_next

 include/net/mptcp.h      |   5 ++
 net/mptcp/pm.c           | 100 +++++++++++++++++++--------------------
 net/mptcp/pm_kernel.c    |  47 ++++++++++++------
 net/mptcp/pm_userspace.c |   9 +++-
 net/mptcp/protocol.h     |  27 ++++++++++-
 net/mptcp/subflow.c      |   6 +--
 6 files changed, 122 insertions(+), 72 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-03-28  4:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  4:01 Geliang Tang [this message]
2025-03-28  4:01 ` [PATCH mptcp-next v6 1/5] mptcp: pm: call pm worker handler without pm lock Geliang Tang
2025-05-06  3:21   ` Geliang Tang
2025-03-28  4:01 ` [PATCH mptcp-next v6 2/5] mptcp: pm: add accept_new_subflow() interface Geliang Tang
2025-03-28  4:01 ` [PATCH mptcp-next v6 3/5] mptcp: pm: add established() interface Geliang Tang
2025-03-28  4:01 ` [PATCH mptcp-next v6 4/5] mptcp: pm: add subflow_established() interface Geliang Tang
2025-03-28  4:01 ` [PATCH mptcp-next v6 5/5] mptcp: pm: drop is_userspace in subflow_check_next Geliang Tang
2025-03-28  5:09 ` [PATCH mptcp-next v6 0/5] BPF path manager, part 6 MPTCP CI
2025-04-08 18:13 ` Matthieu Baerts
2025-04-15  3:16   ` Geliang Tang
2025-04-16  7:29     ` Geliang Tang
2025-04-16  9:42       ` Matthieu Baerts

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.1743133948.git.tanggeliang@kylinos.cn \
    --to=geliang@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=tanggeliang@kylinos.cn \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.