1. 23 1月, 2018 1 次提交
  2. 20 1月, 2018 2 次提交
  3. 15 1月, 2018 4 次提交
  4. 10 1月, 2018 4 次提交
  5. 28 12月, 2017 1 次提交
  6. 21 12月, 2017 2 次提交
    • J
      nfp: bpf: keep track of the offloaded program · d3f89b98
      Jakub Kicinski 提交于
      After TC offloads were converted to callbacks we have no choice
      but keep track of the offloaded filter in the driver.
      
      The check for nn->dp.bpf_offload_xdp was a stop gap solution
      to make sure failed TC offload won't disable XDP, it's no longer
      necessary.  nfp_net_bpf_offload() will return -EBUSY on
      TC vs XDP conflicts.
      
      Fixes: 3f7889c4 ("net: sched: cls_bpf: call block callbacks for offload")
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d3f89b98
    • J
      cls_bpf: fix offload assumptions after callback conversion · 102740bd
      Jakub Kicinski 提交于
      cls_bpf used to take care of tracking what offload state a filter
      is in, i.e. it would track if offload request succeeded or not.
      This information would then be used to issue correct requests to
      the driver, e.g. requests for statistics only on offloaded filters,
      removing only filters which were offloaded, using add instead of
      replace if previous filter was not added etc.
      
      This tracking of offload state no longer functions with the new
      callback infrastructure.  There could be multiple entities trying
      to offload the same filter.
      
      Throw out all the tracking and corresponding commands and simply
      pass to the drivers both old and new bpf program.  Drivers will
      have to deal with offload state tracking by themselves.
      
      Fixes: 3f7889c4 ("net: sched: cls_bpf: call block callbacks for offload")
      Signed-off-by: NJakub Kicinski <jakub.kicinski@netronome.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      102740bd
  7. 16 12月, 2017 1 次提交
  8. 15 12月, 2017 3 次提交
  9. 03 12月, 2017 1 次提交
  10. 05 11月, 2017 4 次提交
  11. 02 11月, 2017 2 次提交
  12. 27 10月, 2017 1 次提交
  13. 21 10月, 2017 2 次提交
  14. 15 10月, 2017 1 次提交
  15. 10 10月, 2017 1 次提交
  16. 04 9月, 2017 1 次提交
  17. 19 8月, 2017 1 次提交
  18. 12 8月, 2017 1 次提交
  19. 08 8月, 2017 4 次提交
  20. 01 6月, 2017 3 次提交