netdev - Re: RFC: dsa: add support for multiple CPU ports

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: <20150312001926.GB9601@lunn.ch>
Date:	Thu, 12 Mar 2015 01:19:26 +0100
From:	Andrew Lunn <andrew@...n.ch>
To:	Mathieu Olivari <mathieu@...eaurora.org>
Cc:	Florian Fainelli <f.fainelli@...il.com>,
	netdev <netdev@...r.kernel.org>,
	Guenter Roeck <linux@...ck-us.net>,
	Jonas Gorski <jogo@...nwrt.org>
Subject: Re: RFC: dsa: add support for multiple CPU ports

> Agreed. The switches I'm talking about (QCA8xxx/AR8xxx) don't support
> a mode which would allow them to use all the CPU ports as one logical
> bonding interface.

I had a 60 second look at https://www.codeaurora.org/cgit/quic/qsdk/oss/lklm/qca-ssdk/

It looks like dess, isis, and isisc have some support for trunks, and
the rest do not.

> I know some of these switches don't even support tagging. So I'd be
> surprised if they're all capable of bonding.

So we are going to end up with multiple solutions depending on what
the hardware is capable of.

> I think DSA should probably support both. I think it should allow
> bonding for switches who support it, but it should also allow for port
> based vlan mapped by the user.

So the question is, how do you make the existing concepts in Linux
support this, so configuration is how you expect it to be, without
special cases, oddities, etc.

	Andrew
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html