All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v15 5/5] mptcp: update userspace pm infos
Date: Wed, 24 May 2023 22:10:56 +0800	[thread overview]
Message-ID: <20230524141056.GA2643@bogon> (raw)
In-Reply-To: <f5b66a5d-4dcc-04a1-76cc-58c872c7ff37@tessares.net>

On Wed, May 24, 2023 at 03:24:09PM +0200, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 24/05/2023 10:02, Geliang Tang wrote:
> > Increase pm subflows counter on both server side and client side when
> > userspace pm creates a new subflow, and decrease the counter when it
> > closes a subflow.
> > 
> > Increase add_addr_signaled counter in mptcp_nl_cmd_announce() when the
> > address is announced by userspace PM.
> > 
> > This modification is similar to how the in-kernel PM is updating the
> > counter: when additional subflows are created/removed.
> (...)
> 
> > diff --git a/net/mptcp/pm_userspace.c b/net/mptcp/pm_userspace.c
> > index 114548b09f47..7ada9cf81c14 100644
> > --- a/net/mptcp/pm_userspace.c
> > +++ b/net/mptcp/pm_userspace.c
> > @@ -91,6 +92,7 @@ static int mptcp_userspace_pm_delete_local_addr(struct mptcp_sock *msk,
> >  
> >  	list_for_each_entry_safe(entry, tmp, &msk->pm.userspace_pm_local_addr_list, list) {
> >  		if (mptcp_addresses_equal(&entry->addr, &addr->addr, false)) {
> > +			msk->pm.local_addr_used--;
> 
> Do you mind if I add this under the following comment with the TODO? We
> should only decrement the entry if it is the last one being used.

Yes, it's much better to move this under the TODO comment.

Thanks,
-Geliang

> 
> >  			/* TODO: a refcount is needed because the entry can
> >  			 * be used multiple times (e.g. fullmesh mode).
> >  			 */
> 
> Cheers,
> Matt
> -- 
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net

  reply	other threads:[~2023-05-24 14:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  8:02 [PATCH mptcp-next v15 0/5] update userspace pm mptcp_info fields part 1 Geliang Tang
2023-05-24  8:02 ` [PATCH mptcp-next v15 1/5] mptcp: only send RM_ADDR in nl_cmd_remove Geliang Tang
2023-05-24  8:02 ` [PATCH mptcp-next v15 2/5] selftests: mptcp: update userspace pm addr tests Geliang Tang
2023-05-24  8:02 ` [PATCH mptcp-next v15 3/5] mptcp: add address into userspace pm list Geliang Tang
2023-05-24  8:43   ` Geliang Tang
2023-05-24 13:21   ` Matthieu Baerts
2023-05-24  8:02 ` [PATCH mptcp-next v15 4/5] selftests: mptcp: update userspace pm subflow tests Geliang Tang
2023-05-24  8:02 ` [PATCH mptcp-next v15 5/5] mptcp: update userspace pm infos Geliang Tang
2023-05-24  9:37   ` mptcp: update userspace pm infos: Tests Results MPTCP CI
2023-05-24 13:24   ` [PATCH mptcp-next v15 5/5] mptcp: update userspace pm infos Matthieu Baerts
2023-05-24 14:10     ` Geliang Tang [this message]
2023-05-24 15:41   ` mptcp: update userspace pm infos: Tests Results MPTCP CI
2023-05-24 16:46   ` MPTCP CI
2023-05-24 13:27 ` [PATCH mptcp-next v15 0/5] update userspace pm mptcp_info fields part 1 Matthieu Baerts
2023-05-24 14:27   ` 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=20230524141056.GA2643@bogon \
    --to=geliang.tang@suse.com \
    --cc=matthieu.baerts@tessares.net \
    --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 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.