aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2016-04-04 21:31:35 -0400
committerDavid S. Miller <davem@davemloft.net>2016-04-04 21:31:35 -0400
commit6e3380488a4769edba0da3b582bb6c070121d784 (patch)
treec054edd2f47a24db2714165e609472fcadec88b4 /tools/perf/scripts/python/call-graph-from-postgresql.py
parent9ef280c6c28f0c01aa9d909263ad47c796713a8e (diff)
parent26892ffc80b4276f6f0d61232a769100023b38ab (diff)
Merge branch 'mv88e6131-hw-bridging-6185'
Vivien Didelot says: ==================== net: dsa: mv88e6131: HW bridging support for 6185 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. Changes v1 -> v2: - Describe the different numbers of databases and prefer a feature-based logic over the current ID/family-based logic. ==================== Tested-by: Andrew Lunn <andrew@lunn.ch> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions