1. 08 8月, 2017 2 次提交
  2. 07 8月, 2017 1 次提交
  3. 03 8月, 2017 1 次提交
  4. 14 6月, 2017 3 次提交
  5. 05 6月, 2017 1 次提交
  6. 02 6月, 2017 1 次提交
  7. 01 6月, 2017 1 次提交
  8. 25 5月, 2017 1 次提交
    • V
      net: dsa: support cross-chip ageing time · 64dba236
      Vivien Didelot 提交于
      Now that the switchdev bridge ageing time attribute is propagated to all
      switch chips of the fabric, each switch can check if the requested value
      is valid and program itself, so that the whole fabric shares a common
      ageing time setting.
      
      This is especially needed for switch chips in between others, containing
      no bridge port members but evidently used in the data path.
      
      To achieve that, remove the condition which skips the other switches. We
      also don't need to identify the target switch anymore, thus remove the
      sw_index member of the dsa_notifier_ageing_time_info notifier structure.
      
      On ZII Dev Rev B (with two 88E6352 and one 88E6185) and ZII Dev Rev C
      (with two 88E6390X), we have the following hardware configuration:
      
          # ip link add name br0 type bridge
          # ip link set master br0 dev lan6
          br0: port 1(lan6) entered blocking state
          br0: port 1(lan6) entered disabled state
          # echo 2000 > /sys/class/net/br0/bridge/ageing_time
      
      Before this patch:
      
          zii-rev-b# cat /sys/kernel/debug/mv88e6xxx/sw*/age_time
          300000
          300000
          15000
      
          zii-rev-c# cat /sys/kernel/debug/mv88e6xxx/sw*/age_time
          300000
          18750
      
      After this patch:
      
          zii-rev-b# cat /sys/kernel/debug/mv88e6xxx/sw*/age_time
          15000
          15000
          15000
      
          zii-rev-c# cat /sys/kernel/debug/mv88e6xxx/sw*/age_time
          18750
          18750
      Signed-off-by: NVivien Didelot <vivien.didelot@savoirfairelinux.com>
      Reviewed-by: NAndrew Lunn <andrew@lunn.ch>
      Reviewed-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      64dba236
  9. 23 5月, 2017 12 次提交
  10. 18 5月, 2017 2 次提交
  11. 21 4月, 2017 1 次提交
  12. 17 4月, 2017 1 次提交
  13. 09 4月, 2017 1 次提交
  14. 08 4月, 2017 1 次提交
  15. 07 2月, 2017 2 次提交
  16. 31 1月, 2017 1 次提交
  17. 30 1月, 2017 2 次提交
  18. 27 1月, 2017 1 次提交
  19. 21 1月, 2017 1 次提交
  20. 08 1月, 2017 1 次提交
  21. 07 1月, 2017 1 次提交
  22. 16 9月, 2016 1 次提交
  23. 09 6月, 2016 1 次提交
    • F
      net: dsa: Initialize CPU port ethtool ops per tree · 0c73c523
      Florian Fainelli 提交于
      Now that we can properly support multiple distinct trees in the system,
      using a global variable: dsa_cpu_port_ethtool_ops is getting clobbered
      as soon as the second switch tree gets probed, and we don't want that.
      
      We need to move this to be dynamically allocated, and since we can't
      really be comparing addresses anymore to determine first time
      initialization versus any other times, just move this to dsa.c and
      dsa2.c where the remainder of the dst/ds initialization happens.
      
      The operations teardown restores the master netdev's ethtool_ops to its
      original ethtool_ops pointer (typically within the Ethernet driver)
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Reviewed-by: NAndrew Lunn <andrew@lunn.ch>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      0c73c523