All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geliang Tang <geliang@kernel.org>
To: Matthieu Baerts <matttbe@kernel.org>,
	MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: [PATCH mptcp-next 1/4] mptcp: pm: netlink: only add server-side attr when true
Date: Thu, 11 Sep 2025 16:45:52 +0800	[thread overview]
Message-ID: <2e5d12513033a5df4310a97a089ff6856ad70178.camel@kernel.org> (raw)
In-Reply-To: <9cd0c8da-96a1-40a1-8b56-1689803a32e7@kernel.org>

On Thu, 2025-09-11 at 10:37 +0200, Matthieu Baerts wrote:
> Hi Geliang,
> 
> On 11/09/2025 10:33, Geliang Tang wrote:
> > Hi Matt,
> > 
> > On Thu, 2025-09-11 at 10:20 +0200, Matthieu Baerts wrote:
> > > Hi Geliang,
> > > 
> > > Thank you for the review!
> > > 
> > > On 11/09/2025 10:15, Geliang Tang wrote:
> > > > Hi Matt,
> > > > 
> > > > On Tue, 2025-09-09 at 18:30 +0200, Matthieu Baerts (NGI0)
> > > > wrote:
> > > > > This attribute is a boolean. No need to add it to set it to
> > > > > 'false'.
> > > > > 
> > > > > Indeed, the default value when this attribute is not set is
> > > > > naturally
> > > > > 'false'. A few bytes can then be saved by not adding this
> > > > > attribute
> > > > > if
> > > > > the connection is not on the server side.
> > > > > 
> > > > > This prepares the future deprecation of its attribute, in
> > > > > favour
> > > > > of a
> > > > > new flag.
> > > > > 
> > > > > Signed-off-by: Matthieu Baerts (NGI0) <matttbe@kernel.org>
> > > > > ---
> > > > >  Documentation/netlink/specs/mptcp_pm.yaml         | 4 ++--
> > > > >  include/uapi/linux/mptcp_pm.h                     | 4 ++--
> > > > >  net/mptcp/pm_netlink.c                            | 4 +++-
> > > > >  tools/testing/selftests/net/mptcp/userspace_pm.sh | 2 +-
> > > > >  4 files changed, 8 insertions(+), 6 deletions(-)
> > > > > 
> > > > > diff --git a/Documentation/netlink/specs/mptcp_pm.yaml
> > > > > b/Documentation/netlink/specs/mptcp_pm.yaml
> > > > > index
> > > > > d1b4829b580ad09baf4afd73b67abd7b4ef6883a..fc47a2931014c0304ef
> > > > > d321
> > > > > 5cc2
> > > > > 4485ea22e1ede 100644
> > > > > --- a/Documentation/netlink/specs/mptcp_pm.yaml
> > > > > +++ b/Documentation/netlink/specs/mptcp_pm.yaml
> > > > > @@ -28,13 +28,13 @@ definitions:
> > > > >            traffic-patterns it can take a long time until the
> > > > >            MPTCP_EVENT_ESTABLISHED is sent.
> > > > >            Attributes: token, family, saddr4 | saddr6, daddr4
> > > > > |
> > > > > daddr6, sport,
> > > > > -          dport, server-side, [flags].
> > > > > +          dport, [server-side], [flags].
> > > > >        -
> > > > >          name: established
> > > > >          doc: >-
> > > > >            A MPTCP connection is established (can start new
> > > > > subflows).
> > > > >            Attributes: token, family, saddr4 | saddr6, daddr4
> > > > > |
> > > > > daddr6, sport,
> > > > > -          dport, server-side, [flags].
> > > > > +          dport, [server-side], [flags].
> > > > >        -
> > > > >          name: closed
> > > > >          doc: >-
> > > > > diff --git a/include/uapi/linux/mptcp_pm.h
> > > > > b/include/uapi/linux/mptcp_pm.h
> > > > > index
> > > > > 7359d34da446b94be148b363079120db03ba8549..bf44a5cf5b5a1e6d789
> > > > > 6326
> > > > > 82a9
> > > > > bedbf8090feb9 100644
> > > > > --- a/include/uapi/linux/mptcp_pm.h
> > > > > +++ b/include/uapi/linux/mptcp_pm.h
> > > > > @@ -16,10 +16,10 @@
> > > > >   *   good time to allocate memory and send ADD_ADDR if
> > > > > needed.
> > > > > Depending on the
> > > > >   *   traffic-patterns it can take a long time until the
> > > > > MPTCP_EVENT_ESTABLISHED
> > > > >   *   is sent. Attributes: token, family, saddr4 | saddr6,
> > > > > daddr4
> > > > > > 
> > > > > daddr6,
> > > > > - *   sport, dport, server-side, [flags].
> > > > > + *   sport, dport, [server-side], [flags].
> > > > >   * @MPTCP_EVENT_ESTABLISHED: A MPTCP connection is
> > > > > established
> > > > > (can
> > > > > start new
> > > > >   *   subflows). Attributes: token, family, saddr4 | saddr6,
> > > > > daddr4 |
> > > > > daddr6,
> > > > > - *   sport, dport, server-side, [flags].
> > > > > + *   sport, dport, [server-side], [flags].
> > > > >   * @MPTCP_EVENT_CLOSED: A MPTCP connection has stopped.
> > > > > Attribute:
> > > > > token.
> > > > >   * @MPTCP_EVENT_ANNOUNCED: A new address has been announced
> > > > > by
> > > > > the
> > > > > peer.
> > > > >   *   Attributes: token, rem_id, family, daddr4 | daddr6 [,
> > > > > dport].
> > > > > diff --git a/net/mptcp/pm_netlink.c b/net/mptcp/pm_netlink.c
> > > > > index
> > > > > 483ddbb9ec406a3e965376ee5a833ae295896a02..33a6bf536c020b59717
> > > > > 472a
> > > > > ca2d
> > > > > 38add26255419 100644
> > > > > --- a/net/mptcp/pm_netlink.c
> > > > > +++ b/net/mptcp/pm_netlink.c
> > > > > @@ -413,7 +413,9 @@ static int mptcp_event_created(struct
> > > > > sk_buff
> > > > > *skb,
> > > > >  	if (err)
> > > > >  		return err;
> > > > >  
> > > > > -	if (nla_put_u8(skb, MPTCP_ATTR_SERVER_SIDE,
> > > > > READ_ONCE(msk-
> > > > > > pm.server_side)))
> > > > > +	/* only set when it is the server side */
> > > > > +	if (READ_ONCE(msk->pm.server_side) &&
> > > > > +	    nla_put_u8(skb, MPTCP_ATTR_SERVER_SIDE, 1))
> > > > 
> > > > In patch 2, this will be modified to use two 'if':
> > > > 
> > > > 	if (READ_ONCE(msk->pm.server_side)) {
> > > > 		flags |= MPTCP_PM_EV_FLAG_SERVER_SIDE;
> > > > 
> > > > 		/* only set when it is the server side */
> > > > 		if (nla_put_u8(skb, MPTCP_ATTR_SERVER_SIDE,
> > > > 1))
> > > > 			return -EMSGSIZE;
> > > > 	}
> > > > 
> > > > Why don't we just use two 'if' statements here, which will make
> > > > patch 2
> > > > simpler:
> > > > 
> > > >        if (READ_ONCE(msk->pm.server_side)) {
> > > >                /* only set when it is the server side */
> > > >                if (nla_put_u8(skb, MPTCP_ATTR_SERVER_SIDE, 1))
> > > >                        return -EMSGSIZE;
> > > >        }
> > > > 
> > > > WDYT?
> > > 
> > > I'm not convinced: that might make the patch 2 simpler, but then
> > > the
> > > patch 1 will raise questions from reviewers and developers
> > > looking at
> > > the patches in the order they have been sent: why using 2 'if'
> > > statements while there is no need to use 2.
> > > 
> > > If we want that, I would have to add something in the commit
> > > message.
> > > I
> > > don't think that's worth it.
> > 
> > Sure. Let's keep this patch as is. If so, could you please update
> > the
> > position of the comments in patch 2 and patch 3? Something like:
> > 
> >         /* only set when it is the server side */
> >         if (READ_ONCE(msk->pm.server_side)) {
> >                 flags |= MPTCP_PM_EV_FLAG_SERVER_SIDE;
> 
> Mmh, I'm not sure: for the flag, it makes sense to only set it when
> it
> is the server side, otherwise that's wrong. Keeping the comment above
> is
> then a bit confusing, no?

If this comment needs to be just above nla_put_u8(), it makes sense to
use 2 'if' here. But up to you.

Thanks,
-Geliang

> 
> > 
> >                 /* Deprecated */
> >                 if (nla_put_u8(skb, MPTCP_ATTR_SERVER_SIDE, 1)) 
> >                         return -EMSGSIZE;
> >         }
> > 
> > Thanks,
> > -Geliang
> > 
> > > 
> > > Cheers,
> > > Matt
> 
> Cheers,
> Matt

  reply	other threads:[~2025-09-11  8:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 16:30 [PATCH mptcp-next 0/4] mptcp: pm: netlink: announce server-side flag Matthieu Baerts (NGI0)
2025-09-09 16:30 ` [PATCH mptcp-next 1/4] mptcp: pm: netlink: only add server-side attr when true Matthieu Baerts (NGI0)
2025-09-11  8:15   ` Geliang Tang
2025-09-11  8:20     ` Matthieu Baerts
2025-09-11  8:33       ` Geliang Tang
2025-09-11  8:37         ` Matthieu Baerts
2025-09-11  8:45           ` Geliang Tang [this message]
2025-09-11  9:28             ` Matthieu Baerts
2025-09-11  9:59               ` Geliang Tang
2025-09-09 16:30 ` [PATCH mptcp-next 2/4] mptcp: pm: netlink: announce server-side flag Matthieu Baerts (NGI0)
2025-09-09 16:30 ` [PATCH mptcp-next 3/4] mptcp: pm: netlink: deprecate server-side attribute Matthieu Baerts (NGI0)
2025-09-09 16:30 ` [PATCH mptcp-next 4/4] selftests: mptcp: pm: get server-side flag Matthieu Baerts (NGI0)
2025-09-11  8:16   ` Geliang Tang
2025-09-11  8:35     ` Matthieu Baerts
2025-09-11  9:04       ` Geliang Tang
2025-09-11  9:35         ` Matthieu Baerts
2025-09-11 10:05           ` Geliang Tang
2025-09-11 10:28             ` Matthieu Baerts
2025-09-09 18:58 ` [PATCH mptcp-next 0/4] mptcp: pm: netlink: announce " MPTCP CI
2025-09-11  8:14 ` Geliang Tang

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=2e5d12513033a5df4310a97a089ff6856ad70178.camel@kernel.org \
    --to=geliang@kernel.org \
    --cc=matttbe@kernel.org \
    --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.