mptcp.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Kishen Maloor <kishen.maloor@intel.com>
To: kishen.maloor@intel.com, mptcp@lists.linux.dev
Subject: [PATCH mptcp-net v3 0/2] mptcp: support MP_PRIO signals with userspace PMs
Date: Tue, 28 Jun 2022 17:29:16 -0400	[thread overview]
Message-ID: <20220628212918.417515-1-kishen.maloor@intel.com> (raw)

This patch series updates MPTCP_PM_CMD_SET_FLAGS to allow userspace PMs
to issue MP_PRIO signals over a selected (by local and remote address+port)
subflow in a MPTCP connection. It also adds self tests for this
change.

This patch series has been rebased to the series (in review) titled
"Locking fixes for subflow flag changes".

v2:
-userspace_pm.sh: added a sleep after issuing the MP_PRIO signal.

v3:
-use local and remote address+port (instead of address ID) alongwith the
connection token to select a subflow.

Kishen Maloor (2):
  mptcp: netlink: issue MP_PRIO signals from userspace PMs
  selftests: mptcp: userspace PM support for MP_PRIO signals

 net/mptcp/pm_netlink.c                        | 30 ++++++--
 net/mptcp/pm_userspace.c                      | 30 ++++++++
 net/mptcp/protocol.h                          |  8 +-
 tools/testing/selftests/net/mptcp/pm_nl_ctl.c | 73 ++++++++++++++++++-
 .../selftests/net/mptcp/userspace_pm.sh       | 32 ++++++++
 5 files changed, 165 insertions(+), 8 deletions(-)

--
2.31.1

             reply	other threads:[~2022-06-28 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 21:29 Kishen Maloor [this message]
2022-06-28 21:29 ` [PATCH mptcp-net v3 1/2] mptcp: netlink: issue MP_PRIO signals from userspace PMs Kishen Maloor
2022-06-28 22:57   ` Mat Martineau
2022-06-28 23:53     ` Kishen Maloor
2022-06-28 21:29 ` [PATCH mptcp-net v3 2/2] selftests: mptcp: userspace PM support for MP_PRIO signals Kishen Maloor

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=20220628212918.417515-1-kishen.maloor@intel.com \
    --to=kishen.maloor@intel.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;
as well as URLs for NNTP newsgroup(s).