lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231012192738.34ed1f19@hermes.local>
Date:   Thu, 12 Oct 2023 19:27:38 -0700
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     Florian Fainelli <florian.fainelli@...adcom.com>,
        netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Broadcom internal kernel review list 
        <bcm-kernel-feedback-list@...adcom.com>,
        "open list:ARM/Mediatek SoC support" <linux-kernel@...r.kernel.org>,
        "moderated list:ARM/Mediatek SoC support" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH net-next v2 1/2] net: dsa: Use conduit and user terms

On Fri, 13 Oct 2023 02:10:29 +0300
Vladimir Oltean <olteanv@...il.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ