netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Vladimir Oltean <vladimir.oltean@nxp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	David Ahern <dsahern@kernel.org>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master
Date: Thu, 22 Sep 2022 08:27:24 -0700	[thread overview]
Message-ID: <20220922082724.7abb328a@hermes.local> (raw)
In-Reply-To: <20220922062405.15837cfe@kernel.org>

On Thu, 22 Sep 2022 06:24:05 -0700
Jakub Kicinski <kuba@kernel.org> wrote:

> On Thu, 22 Sep 2022 03:30:43 +0200 Andrew Lunn wrote:
> > Looking at these, none really fit the concept of what the master
> > interface is.
> > 
> > slave is also used quite a lot within DSA, but we can probably use
> > user in place of that, it is already somewhat used as a synonym within
> > DSA terminology.
> > 
> > Do you have any more recommendations for something which pairs with
> > user.   
> 
> cpu-ifc? via?

I did look at the Switch Abstraction Layer document which
started at Microsoft for Sonic and is now part of Open Compute.

Didn't see anything there. The 802 spec uses words like
aggregator port etc.

  reply	other threads:[~2022-09-22 15:27 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-21 16:51 [PATCH v2 iproute2-next] ip link: add sub-command to view and change DSA master Vladimir Oltean
2022-09-21 18:36 ` Stephen Hemminger
2022-09-21 18:38   ` Vladimir Oltean
2022-09-21 22:33     ` Stephen Hemminger
2022-09-22 14:41       ` Vladimir Oltean
2022-09-22 15:30         ` Stephen Hemminger
2022-09-22 15:42         ` Andrew Lunn
2022-09-22 18:43           ` Vladimir Oltean
2022-09-22 19:04             ` Stephen Hemminger
2022-09-22 19:36               ` Vladimir Oltean
2022-09-22 20:34                 ` Andrew Lunn
2022-09-22 21:25                   ` Florian Fainelli
2022-09-22 21:28                     ` Vladimir Oltean
2022-09-22 21:30                       ` Florian Fainelli
2022-09-22 21:40                         ` Vladimir Oltean
2022-09-22 21:41                         ` Andrew Lunn
2022-09-22 21:52                           ` Vladimir Oltean
2022-09-21 22:41     ` Stephen Hemminger
2022-09-22  1:30       ` Andrew Lunn
2022-09-22 13:24         ` Jakub Kicinski
2022-09-22 15:27           ` Stephen Hemminger [this message]
2022-09-22 15:36             ` Florian Fainelli
2022-09-22 18:00           ` Vladimir Oltean
2022-09-22 19:30             ` Jakub Kicinski
2022-09-22 20:13               ` Vladimir Oltean
2022-09-22 20:28                 ` Stephen Hemminger
2022-09-22 20:36                   ` Vladimir Oltean
2022-09-22 21:28                     ` Florian Fainelli

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=20220922082724.7abb328a@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=andrew@lunn.ch \
    --cc=dsahern@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.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;
as well as URLs for NNTP newsgroup(s).