From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
David Ahern <dsahern@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH iproute2] ip link: add sub-command to view and change DSA master
Date: Tue, 6 Sep 2022 19:13:56 +0000 [thread overview]
Message-ID: <20220906191355.bnimmq4z36p5yivo@skbuf> (raw)
In-Reply-To: <20220906095517.4022bde6@hermes.local>
On Tue, Sep 06, 2022 at 09:55:17AM -0700, Stephen Hemminger wrote:
> > > Using the term master is an unfortunate choice.
> > > Although it is common practice in Linux it is not part of any
> > > current standard and goes against the Linux Foundation non-inclusive
> > > naming policy.
> >
> > Concretely, what is it that you propose?
>
> Maybe "switch" instead of "master"?
"Switch" and "DSA master" are not interchangeable concepts. A DSA master
is a regular Ethernet controller that is connected to a local (onboard
or embedded) switch and handles its management traffic. The use of the
term has existed since the introduction of DSA in 2008 and has reached a
wide audience among users through the papers that popularized DSA later, mainly
https://legacy.netdevconf.info/2.1/papers/distributed-switch-architecture.pdf
Whereas a switch is a multi-port Ethernet device that handles L2
forwarding by MAC DA and VLAN ID, essentially containing a hardware
implementation of the Linux bridge.
[ Alternative answer: how about "schnauzer"? I always liked how that word sounds. ]
next prev parent reply other threads:[~2022-09-06 19:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 19:00 [PATCH iproute2] ip link: add sub-command to view and change DSA master Vladimir Oltean
2022-09-06 15:29 ` Stephen Hemminger
2022-09-06 16:41 ` Vladimir Oltean
2022-09-06 16:55 ` Stephen Hemminger
2022-09-06 19:13 ` Vladimir Oltean [this message]
2022-09-06 20:05 ` Andrew Lunn
2022-09-06 20:33 ` Florian Fainelli
2022-09-06 21:17 ` Stephen Hemminger
2022-09-06 21:34 ` Florian Fainelli
2022-09-06 21:37 ` Andrew Lunn
2022-09-08 12:51 ` Vladimir Oltean
2022-09-08 14:08 ` David Ahern
2022-09-08 14:25 ` Stephen Hemminger
2022-09-08 16:11 ` Vladimir Oltean
2022-09-08 16:35 ` Florian Fainelli
2022-09-08 16:39 ` Stephen Hemminger
2022-09-09 6:09 ` Benjamin Poirier
2022-09-09 11:23 ` Vladimir Oltean
2022-09-09 15:03 ` 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=20220906191355.bnimmq4z36p5yivo@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=andrew@lunn.ch \
--cc=dsahern@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=vivien.didelot@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox