All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Baerts <matthieu.baerts@tessares.net>
To: Geliang Tang <geliang.tang@suse.com>, mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next v2] mptcp: update userspace pm subflows info
Date: Wed, 25 Jan 2023 19:13:31 +0100	[thread overview]
Message-ID: <5d756f95-0a7e-fd18-ccf8-4c206b5621d6@tessares.net> (raw)
In-Reply-To: <d262f6beb6899f0a79acbeb1d3c8c855e95e098a.1673599496.git.geliang.tang@suse.com>

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?

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 :)

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.

Cheers,
Matt
-- 
Tessares | Belgium | Hybrid Access Solutions
www.tessares.net

  parent reply	other threads:[~2023-01-25 18:13 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 ` Matthieu Baerts [this message]
2023-01-28  2:44   ` [PATCH mptcp-next v2] mptcp: update userspace pm subflows info Geliang Tang
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=5d756f95-0a7e-fd18-ccf8-4c206b5621d6@tessares.net \
    --to=matthieu.baerts@tessares.net \
    --cc=geliang.tang@suse.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 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.