MPTCP Linux Development
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Geliang Tang <geliangtang@gmail.com>
Cc: mptcp@lists.linux.dev, Geliang Tang <geliangtang@xiaomi.com>
Subject: Re: [MPTCP][PATCH mptcp-next] Squash to "mptcp: remote addresses fullmesh"
Date: Wed, 28 Jul 2021 17:20:53 -0700 (PDT)	[thread overview]
Message-ID: <fee96eb-d19-1611-79b-34c580ad93c4@linux.intel.com> (raw)
In-Reply-To: <f5e079bf977b0c9e05e26f6b90d8cde4bb9a6c9f.1627463618.git.geliangtang@xiaomi.com>

On Wed, 28 Jul 2021, Geliang Tang wrote:

> From: Geliang Tang <geliangtang@xiaomi.com>
>
> Fix the checkpatch.pl warning:
> WARNING: networking block comments don't use an empty /* line, use /* Comment...
> #63: FILE: net/mptcp/pm_netlink.c:427:
> +/*
> + * Fill all the remote addresses into the array addrs[],
>
> And some more cleanups.
>
> Signed-off-by: Geliang Tang <geliangtang@xiaomi.com>

Thanks Geliang.

Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>


> ---
> net/mptcp/pm_netlink.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> index ecf43d45711a..8eeae401c83f 100644
> --- a/net/mptcp/pm_netlink.c
> +++ b/net/mptcp/pm_netlink.c
> @@ -423,8 +423,7 @@ static bool lookup_address_in_vec(struct mptcp_addr_info *addrs, unsigned int nr
> 	return false;
> }
>
> -/*
> - * Fill all the remote addresses into the array addrs[],
> +/* Fill all the remote addresses into the array addrs[],
>  * and return the array size.
>  */
> static unsigned int fill_remote_addresses_vec(struct mptcp_sock *msk, bool fullmesh,
> @@ -440,7 +439,9 @@ static unsigned int fill_remote_addresses_vec(struct mptcp_sock *msk, bool fullm
> 	pernet = net_generic(sock_net(sk), pm_nl_pernet_id);
> 	subflows_max = mptcp_pm_get_subflows_max(msk);
>
> -	/* non-fullmesh, fill in the remote address */
> +	/* Non-fullmesh endpoint, fill in the single entry
> +	 * corresponding to the primary MPC subflow remote address
> +	 */
> 	if (!fullmesh) {
> 		remote_address((struct sock_common *)sk, &remote);
> 		msk->pm.subflows++;
> @@ -505,14 +506,13 @@ static void mptcp_pm_create_subflow_or_signal_addr(struct mptcp_sock *msk)
> 	    !READ_ONCE(msk->pm.remote_deny_join_id0)) {
> 		local = select_local_address(pernet, msk);
> 		if (local) {
> +			bool fullmesh = !!(local->flags & MPTCP_PM_ADDR_FLAG_FULLMESH);
> 			struct mptcp_addr_info addrs[MPTCP_PM_ADDR_MAX];
> 			int i, nr;
>
> 			msk->pm.local_addr_used++;
> 			check_work_pending(msk);
> -			nr = fill_remote_addresses_vec(msk,
> -						       local->flags & MPTCP_PM_ADDR_FLAG_FULLMESH,
> -						       addrs);
> +			nr = fill_remote_addresses_vec(msk, fullmesh, addrs);
> 			spin_unlock_bh(&msk->pm.lock);
> 			for (i = 0; i < nr; i++) {
> 				__mptcp_subflow_connect(sk, &local->addr, &addrs[i],
> -- 
> 2.31.1
>
>
>

--
Mat Martineau
Intel

      parent reply	other threads:[~2021-07-29  0:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-28  9:16 [MPTCP][PATCH mptcp-next] Squash to "mptcp: remote addresses fullmesh" Geliang Tang
2021-07-28  9:16 ` [MPTCP][PATCH mptcp-next] Squash to "mptcp: local " Geliang Tang
2021-07-29  0:21   ` Mat Martineau
2021-07-29  0:20 ` Mat Martineau [this message]

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=fee96eb-d19-1611-79b-34c580ad93c4@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=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