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
| ||
|
Date: Mon, 4 Apr 2016 04:13:13 +0200 From: Andrew Lunn <andrew@...n.ch> To: Vivien Didelot <vivien.didelot@...oirfairelinux.com> Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, kernel@...oirfairelinux.com, "David S. Miller" <davem@...emloft.net> Subject: Re: [PATCH net-next v2 0/6] net: dsa: mv88e6131: HW bridging support for 6185 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@...n.ch> Andrew
Powered by blists - more mailing lists