All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
	netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	"open list:ARM/Mediatek SoC support"
	<linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v2 1/2] net: dsa: Use conduit and user terms
Date: Thu, 12 Oct 2023 19:27:38 -0700	[thread overview]
Message-ID: <20231012192738.34ed1f19@hermes.local> (raw)
In-Reply-To: <20231012231029.tqz3e5dnlvbmcmja@skbuf>

On Fri, 13 Oct 2023 02:10:29 +0300
Vladimir Oltean <olteanv@gmail.com> wrote:

> >  Secondly, it is possible to perform load balancing between CPU ports on a per
> >  packet basis, rather than statically assigning user ports to CPU ports.
> > -This can be achieved by placing the DSA masters under a LAG interface (bonding
> > +This can be achieved by placing the DSA conduits under a LAG interface (bonding
> >  or team). DSA monitors this operation and creates a mirror of this software LAG
> > -on the CPU ports facing the physical DSA masters that constitute the LAG slave
> > +on the CPU ports facing the physical DSA conduits that constitute the LAG user  
> 
> Replacing "LAG slave devices" with "LAG user devices" wasn't warranted,
> and it alters the meaning.

The term slave is not in the IEEE 802 standard.
Most other implementations use member instead of slave.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Hemminger <stephen@networkplumber.org>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
	netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Broadcom internal kernel review list 
	<bcm-kernel-feedback-list@broadcom.com>,
	"open list:ARM/Mediatek SoC support"
	<linux-kernel@vger.kernel.org>,
	"moderated list:ARM/Mediatek SoC support" 
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH net-next v2 1/2] net: dsa: Use conduit and user terms
Date: Thu, 12 Oct 2023 19:27:38 -0700	[thread overview]
Message-ID: <20231012192738.34ed1f19@hermes.local> (raw)
In-Reply-To: <20231012231029.tqz3e5dnlvbmcmja@skbuf>

On Fri, 13 Oct 2023 02:10:29 +0300
Vladimir Oltean <olteanv@gmail.com> wrote:

> >  Secondly, it is possible to perform load balancing between CPU ports on a per
> >  packet basis, rather than statically assigning user ports to CPU ports.
> > -This can be achieved by placing the DSA masters under a LAG interface (bonding
> > +This can be achieved by placing the DSA conduits under a LAG interface (bonding
> >  or team). DSA monitors this operation and creates a mirror of this software LAG
> > -on the CPU ports facing the physical DSA masters that constitute the LAG slave
> > +on the CPU ports facing the physical DSA conduits that constitute the LAG user  
> 
> Replacing "LAG slave devices" with "LAG user devices" wasn't warranted,
> and it alters the meaning.

The term slave is not in the IEEE 802 standard.
Most other implementations use member instead of slave.

  reply	other threads:[~2023-10-13  2:28 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 22:20 [PATCH net-next v2 0/2] Switch DSA to inclusive terminology Florian Fainelli
2023-10-11 22:20 ` Florian Fainelli
2023-10-11 22:20 ` [PATCH net-next v2 1/2] net: dsa: Use conduit and user terms Florian Fainelli
2023-10-11 22:20   ` Florian Fainelli
2023-10-12 21:23   ` Andrew Lunn
2023-10-12 21:23     ` Andrew Lunn
2023-10-12 23:10   ` Vladimir Oltean
2023-10-12 23:10     ` Vladimir Oltean
2023-10-13  2:27     ` Stephen Hemminger [this message]
2023-10-13  2:27       ` Stephen Hemminger
2023-10-13 16:25     ` Stephen Hemminger
2023-10-13 16:25       ` Stephen Hemminger
2023-10-13 16:27       ` Florian Fainelli
2023-10-13 16:27         ` Florian Fainelli
2023-10-23  7:12   ` Pavel Machek
2023-10-23  7:12     ` Pavel Machek
2023-10-23 15:50     ` Florian Fainelli
2023-10-23 15:50       ` Florian Fainelli
2023-10-23 19:32     ` Vladimir Oltean
2023-10-23 19:32       ` Vladimir Oltean
2023-10-11 22:20 ` [PATCH net-next v2 2/2] net: dsa: Rename IFLA_DSA_MASTER to IFLA_DSA_CONDUIT Florian Fainelli
2023-10-11 22:20   ` Florian Fainelli
2023-10-11 23:30   ` Stephen Hemminger
2023-10-11 23:30     ` Stephen Hemminger
2023-10-12 23:13     ` Vladimir Oltean
2023-10-12 23:13       ` Vladimir Oltean
2023-10-13  2:30       ` Stephen Hemminger
2023-10-13  2:30         ` Stephen Hemminger
2023-10-11 23:22 ` [PATCH net-next v2 0/2] Switch DSA to inclusive terminology Stephen Hemminger
2023-10-11 23:22   ` Stephen Hemminger

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=20231012192738.34ed1f19@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=andrew@lunn.ch \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    /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.