[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150313015710.GA13593@codeaurora.org>
Date: Thu, 12 Mar 2015 18:57:10 -0700
From: Mathieu Olivari <mathieu@...eaurora.org>
To: Andrew Lunn <andrew@...n.ch>
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
On Thu, Mar 12, 2015 at 01:19:26AM +0100, Andrew Lunn wrote:
> > 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.
>
Yes, they do. But not on the CPU port, unfortunately.
> > 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.
>
I'll start by ignoring the second CPU port for now and see how far I go.
> 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
Powered by blists - more mailing lists