1. 12 8月, 2015 1 次提交
  2. 10 8月, 2015 2 次提交
  3. 21 7月, 2015 2 次提交
  4. 12 7月, 2015 1 次提交
  5. 24 6月, 2015 1 次提交
  6. 23 6月, 2015 4 次提交
  7. 12 6月, 2015 1 次提交
  8. 11 6月, 2015 1 次提交
    • S
      switchdev: fix handling for drivers not supporting IPv4 fib add/del ops · af201f72
      Scott Feldman 提交于
      If CONFIG_NET_SWITCHDEV is enabled, but port driver does not implement
      support for IPv4 FIB add/del ops, don't fail route add/del offload
      operations.  Route adds will not be marked as OFFLOAD.  Routes will be
      installed in the kernel FIB, as usual.
      
      This was report/fixed by Florian when testing DSA driver with net-next on
      devices with L2 offload support but no L3 offload support. What he reported
      was an initial route installed from DHCP client would fail (route not
      installed to kernel FIB).  This was triggering the setting of
      ipv4.fib_offload_disabled, which would disable route offloading after the
      first failure.  So subsequent attempts to install the route would succeed.
      
      There is follow-on work/discussion to address the handling of route install
      failures, but for now, let's differentiate between no support and failed
      support.
      Reported-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NScott Feldman <sfeldma@gmail.com>
      Signed-off-by: NFlorian Fainelli <f.fainelli@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      af201f72
  9. 04 6月, 2015 1 次提交
  10. 18 5月, 2015 1 次提交
  11. 15 5月, 2015 1 次提交
  12. 14 5月, 2015 3 次提交
  13. 13 5月, 2015 12 次提交
  14. 24 3月, 2015 1 次提交
  15. 16 3月, 2015 1 次提交
  16. 12 3月, 2015 1 次提交
  17. 10 3月, 2015 2 次提交
  18. 07 3月, 2015 1 次提交
  19. 06 3月, 2015 3 次提交
    • S
      fib: hook IPv4 fib for hardware offload · 8e05fd71
      Scott Feldman 提交于
      Call into the switchdev driver any time an IPv4 fib entry is
      added/modified/deleted from the kernel's FIB.  The switchdev driver may or
      may not install the route to the offload device.  In the case where the
      driver tries to install the route and something goes wrong (device's routing
      table is full, etc), then all of the offloaded routes will be flushed from the
      device, route forwarding falls back to the kernel, and no more routes are
      offloading.
      
      We can refine this logic later.  For now, use the simplist model of offloading
      routes up to the point of failure, and then on failure, undo everything and
      mark IPv4 offloading disabled.
      Signed-off-by: NScott Feldman <sfeldma@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      8e05fd71
    • S
      switchdev: implement IPv4 fib ndo wrappers · b5d6fbde
      Scott Feldman 提交于
      Flesh out ndo wrappers to call into device driver.  To call into device driver,
      the wrapper must interate over route's nexthops to ensure all nexthop devs
      belong to the same switch device.  Currently, there is no support for route's
      nexthops spanning offloaded and non-offloaded devices, or spanning ports of
      multiple offload devices.
      
      Since switch device ports may be stacked under virtual interfaces (bonds and/or
      bridges), and the route's nexthop may be on the virtual interface, the wrapper
      will traverse the nexthop dev down to the base dev.  It's the base dev that's
      passed to the switchdev driver's ndo ops.
      Signed-off-by: NScott Feldman <sfeldma@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b5d6fbde
    • S
      switchdev: don't support custom ip rules, for now · 104616e7
      Scott Feldman 提交于
      Keep switchdev FIB offload model simple for now and don't allow custom ip
      rules.
      Signed-off-by: NScott Feldman <sfeldma@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      104616e7