From: Geliang Tang <geliang.tang@suse.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2] mptcp: update userspace pm subflows info
Date: Sat, 28 Jan 2023 10:44:49 +0800 [thread overview]
Message-ID: <20230128024449.GA3720@bogon> (raw)
In-Reply-To: <5d756f95-0a7e-fd18-ccf8-4c206b5621d6@tessares.net>
On Wed, Jan 25, 2023 at 07:13:31PM +0100, Matthieu Baerts wrote:
> Hi Geliang,
>
> On 13/01/2023 09:45, Geliang Tang wrote:
> > Increase pm subflows counter when userspace pm creates a new subflow,
> > and decrease the counter when it closes a subflow.
> >
> > Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/329
>
> (sorry for the delay)
>
> Thank you, the patch looks good to me! But I don't think it is enough to
> close the ticket 329.
>
> I think there are other fields visible in `MPTCP_INFO` but only updated
> by the in-kernel PM. e.g.
>
> - add_addr_signaled
> - add_addr_accepted
> - local_addr_used
>
> I guess these counters should be modified as well (in different
> commits), no?
Yes, I'll modify these counters in v3.
>
> Also, I don't know if we should consider this as a "new feature" for
> net-next: to me, it looks like we forgot to update the counters and it
> is not really a new feature to update them but more a bug-fix. So maybe
> we can target -net? I'm open to suggestions on that point :)
Sure. I'll update this in v3.
>
> Not directly related but for the issue #330 -- 'subflows' counters not
> incremented for the server side -- it could be considered as a bug fix
> as well depending on how it is implemented: if it is backported, we
> would have the same behaviour with all kernels. Or we add new field(s)
> in MPTCP_INFO but this is maybe not needed.
OK, I'll address #330 in v3 too.
Thanks,
-Geliang
>
> Cheers,
> Matt
> --
> Tessares | Belgium | Hybrid Access Solutions
> www.tessares.net
next prev parent reply other threads:[~2023-01-28 2:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 8:45 [PATCH mptcp-next v2] mptcp: update userspace pm subflows info Geliang Tang
2023-01-13 9:51 ` mptcp: update userspace pm subflows info: Tests Results MPTCP CI
2023-01-25 18:13 ` [PATCH mptcp-next v2] mptcp: update userspace pm subflows info Matthieu Baerts
2023-01-28 2:44 ` Geliang Tang [this message]
2023-01-28 13:54 ` 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=20230128024449.GA3720@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.