Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1370328 > unrolled thread
| Started by | Andrew Lunn <andrew@lunn.ch> |
|---|---|
| First post | 2016-04-04 04:20 +0200 |
| Last post | 2016-04-05 03:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 Andrew Lunn <andrew@lunn.ch> - 2016-04-04 04:20 +0200
Re: [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 David Miller <davem@davemloft.net> - 2016-04-05 03:40 +0200
| From | Andrew Lunn <andrew@lunn.ch> |
|---|---|
| Date | 2016-04-04 04:20 +0200 |
| Subject | Re: [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 |
| Message-ID | <rk2hr-4uV-1@gated-at.bofh.it> |
On Thu, Mar 31, 2016 at 04:53:40PM -0400, Vivien Didelot wrote: > All packets passing through a switch of the 6185 family are currently all > directed to the CPU port. This means that port bridging is software driven. > > To enable hardware bridging for this switch family, we need to implement the > port mapping operations, the FDB operations, and optionally the VLAN operations > (for 802.1Q and VLAN filtering aware systems). > > However this family only has 256 FDBs indexed by 8-bit identifiers, opposed to > 4096 FDBs with 12-bit identifiers for other families such as 6352. It also > doesn't have dedicated FID registers for ATU and VTU operations. > > This patchset fixes these differences, and enable hardware bridging for 6185. Hi Vivien I added a test for in chip 6185 bridging, and it worked as expected. Tested-by: Andrew Lunn <andrew@lunn.ch> Andrew
[toc] | [next] | [standalone]
| From | David Miller <davem@davemloft.net> |
|---|---|
| Date | 2016-04-05 03:40 +0200 |
| Subject | Re: [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 |
| Message-ID | <rko8i-3C9-3@gated-at.bofh.it> |
| In reply to | #1370328 |
From: Andrew Lunn <andrew@lunn.ch> Date: Mon, 4 Apr 2016 04:13:13 +0200 > On Thu, Mar 31, 2016 at 04:53:40PM -0400, Vivien Didelot wrote: >> All packets passing through a switch of the 6185 family are currently all >> directed to the CPU port. This means that port bridging is software driven. >> >> To enable hardware bridging for this switch family, we need to implement the >> port mapping operations, the FDB operations, and optionally the VLAN operations >> (for 802.1Q and VLAN filtering aware systems). >> >> However this family only has 256 FDBs indexed by 8-bit identifiers, opposed to >> 4096 FDBs with 12-bit identifiers for other families such as 6352. It also >> doesn't have dedicated FID registers for ATU and VTU operations. >> >> This patchset fixes these differences, and enable hardware bridging for 6185. > > Hi Vivien > > I added a test for in chip 6185 bridging, and it worked as expected. > > Tested-by: Andrew Lunn <andrew@lunn.ch> Series applied to net-next, thanks.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web