Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-12-01 Thread Florian Fainelli
On 11/23/2016 05:48 AM, Ido Schimmel wrote: > Hi Florian, > > On Tue, Nov 22, 2016 at 09:56:30AM -0800, Florian Fainelli wrote: >> On 11/22/2016 09:41 AM, Ido Schimmel wrote: >>> Hi Florian, >>> >>> On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: Hi all, This patch

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-23 Thread Ido Schimmel
Hi Florian, On Tue, Nov 22, 2016 at 09:56:30AM -0800, Florian Fainelli wrote: > On 11/22/2016 09:41 AM, Ido Schimmel wrote: > > Hi Florian, > > > > On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: > >> Hi all, > >> > >> This patch series allows using the bridge master interface t

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-23 Thread Jiri Pirko
Wed, Nov 23, 2016 at 01:24:30AM CET, f.faine...@gmail.com wrote: >On 11/22/2016 02:08 PM, Jiri Pirko wrote: >> Tue, Nov 22, 2016 at 06:48:29PM CET, and...@lunn.ch wrote: >>> Hi Ido >>> First of all, I want to be sure that when we say "CPU port", we're talking about the same thing. In mlxs

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Florian Fainelli
On 11/22/2016 02:08 PM, Jiri Pirko wrote: > Tue, Nov 22, 2016 at 06:48:29PM CET, and...@lunn.ch wrote: >> Hi Ido >> >>> First of all, I want to be sure that when we say "CPU port", we're >>> talking about the same thing. In mlxsw, the CPU port is a pipe between >>> the device and the host, through

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Jiri Pirko
Tue, Nov 22, 2016 at 06:48:29PM CET, and...@lunn.ch wrote: >Hi Ido > >> First of all, I want to be sure that when we say "CPU port", we're >> talking about the same thing. In mlxsw, the CPU port is a pipe between >> the device and the host, through which all packets trapped to the host >> go throu

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Florian Fainelli
On 11/22/2016 09:41 AM, Ido Schimmel wrote: > Hi Florian, > > On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: >> Hi all, >> >> This patch series allows using the bridge master interface to configure >> an Ethernet switch port's CPU/management port with different VLAN attributes

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Ido Schimmel
Hi Florian, On Mon, Nov 21, 2016 at 11:09:22AM -0800, Florian Fainelli wrote: > Hi all, > > This patch series allows using the bridge master interface to configure > an Ethernet switch port's CPU/management port with different VLAN attributes > than > those of the bridge downstream ports/members

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Andrew Lunn
Hi Ido > First of all, I want to be sure that when we say "CPU port", we're > talking about the same thing. In mlxsw, the CPU port is a pipe between > the device and the host, through which all packets trapped to the host > go through. So, when a packet is trapped, the driver reads its Rx > descr

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Vivien Didelot
Hi Florian, Florian Fainelli writes: > This patch series allows using the bridge master interface to configure > an Ethernet switch port's CPU/management port with different VLAN attributes > than > those of the bridge downstream ports/members. > > Jiri, Ido, Andrew, Vivien, please review the i

Re: [RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-22 Thread Jiri Pirko
Mon, Nov 21, 2016 at 08:09:22PM CET, f.faine...@gmail.com wrote: >Hi all, > >This patch series allows using the bridge master interface to configure >an Ethernet switch port's CPU/management port with different VLAN attributes >than >those of the bridge downstream ports/members. > >Jiri, Ido, Andr

[RFC net-next 0/3] net: bridge: Allow CPU port configuration

2016-11-21 Thread Florian Fainelli
Hi all, This patch series allows using the bridge master interface to configure an Ethernet switch port's CPU/management port with different VLAN attributes than those of the bridge downstream ports/members. Jiri, Ido, Andrew, Vivien, please review the impact on mlxsw and mv88e6xxx, I tested thi