From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Kishen Maloor <kishen.maloor@intel.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-net v4 0/2] mptcp: support MP_PRIO signals with userspace PMs
Date: Tue, 28 Jun 2022 20:37:12 -0700 (PDT) [thread overview]
Message-ID: <144ee4af-c481-ffd3-1eae-151557d28e9c@linux.intel.com> (raw)
In-Reply-To: <20220629012702.425574-1-kishen.maloor@intel.com>
On Tue, 28 Jun 2022, Kishen Maloor wrote:
> 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.
>
> v4:
> -fixed bug during rebase in v3.
Thanks Kishen. v4 looks good to me, and the builds look good (I pushed
equivalent commits to github to trigger a build):
https://cirrus-ci.com/build/6289402744799232
https://github.com/multipath-tcp/mptcp_net-next/runs/7103422638
Looks like the github action got a little confused by the exact version of
the patches not being in patchwork.
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
At the meeting last week Paolo said he was planning to take a look as
well.
>
> 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
>
>
--
Mat Martineau
Intel
next prev parent reply other threads:[~2022-06-29 3:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 1:27 [PATCH mptcp-net v4 0/2] mptcp: support MP_PRIO signals with userspace PMs Kishen Maloor
2022-06-29 1:27 ` [PATCH mptcp-net v4 1/2] mptcp: netlink: issue MP_PRIO signals from " Kishen Maloor
2022-06-29 1:27 ` [PATCH mptcp-net v4 2/2] selftests: mptcp: userspace PM support for MP_PRIO signals Kishen Maloor
2022-06-29 3:37 ` Mat Martineau [this message]
2022-06-29 10:16 ` [PATCH mptcp-net v4 0/2] mptcp: support MP_PRIO signals with userspace PMs Paolo Abeni
2022-06-29 16:03 ` Mat Martineau
2022-06-30 17:46 ` 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=144ee4af-c481-ffd3-1eae-151557d28e9c@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=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