1. 02 6月, 2020 1 次提交
  2. 31 3月, 2020 1 次提交
    • J
      net: sched: expose HW stats types per action used by drivers · 93a129eb
      Jiri Pirko 提交于
      It may be up to the driver (in case ANY HW stats is passed) to select
      which type of HW stats he is going to use. Add an infrastructure to
      expose this information to user.
      
      $ tc filter add dev enp3s0np1 ingress proto ip handle 1 pref 1 flower dst_ip 192.168.1.1 action drop
      $ tc -s filter show dev enp3s0np1 ingress
      filter protocol ip pref 1 flower chain 0
      filter protocol ip pref 1 flower chain 0 handle 0x1
        eth_type ipv4
        dst_ip 192.168.1.1
        in_hw in_hw_count 2
              action order 1: gact action drop
               random type none pass val 0
               index 1 ref 1 bind 1 installed 10 sec used 10 sec
              Action statistics:
              Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0)
              backlog 0b 0p requeues 0
              used_hw_stats immediate     <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
      Signed-off-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      93a129eb
  3. 18 3月, 2020 1 次提交
  4. 09 3月, 2020 1 次提交
  5. 27 2月, 2020 1 次提交
  6. 14 11月, 2019 1 次提交
  7. 01 11月, 2019 4 次提交
  8. 31 8月, 2019 1 次提交
  9. 19 8月, 2019 2 次提交
    • S
      bnxt_en: Fix to include flow direction in L2 key · 9bf46566
      Somnath Kotur 提交于
      FW expects the driver to provide unique flow reference handles
      for Tx or Rx flows. When a Tx flow and an Rx flow end up sharing
      a reference handle, flow offload does not seem to work.
      This could happen in the case of 2 flows having their L2 fields
      wildcarded but in different direction.
      Fix to incorporate the flow direction as part of the L2 key
      
      v2: Move the dir field to the end of the bnxt_tc_l2_key struct to
      fix the warning reported by kbuild test robot <lkp@intel.com>.
      There is existing code that initializes the structure using
      nested initializer and will warn with the new u8 field added to
      the beginning.  The structure also packs nicer when this new u8 is
      added to the end of the structure [MChan].
      
      Fixes: abd43a13 ("bnxt_en: Support for 64-bit flow handle.")
      Signed-off-by: NSomnath Kotur <somnath.kotur@broadcom.com>
      Signed-off-by: NMichael Chan <michael.chan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9bf46566
    • V
      bnxt_en: Use correct src_fid to determine direction of the flow · 685ec6a8
      Venkat Duvvuru 提交于
      Direction of the flow is determined using src_fid. For an RX flow,
      src_fid is PF's fid and for TX flow, src_fid is VF's fid. Direction
      of the flow must be specified, when getting statistics for that flow.
      Currently, for DECAP flow, direction is determined incorrectly, i.e.,
      direction is initialized as TX for DECAP flow, instead of RX. Because
      of which, stats are not reported for this DECAP flow, though it is
      offloaded and there is traffic for that flow, resulting in flow age out.
      
      This patch fixes the problem by determining the DECAP flow's direction
      using correct fid.  Set the flow direction in all cases for consistency
      even if 64-bit flow handle is not used.
      
      Fixes: abd43a13 ("bnxt_en: Support for 64-bit flow handle.")
      Signed-off-by: NVenkat Duvvuru <venkatkumar.duvvuru@broadcom.com>
      Signed-off-by: NMichael Chan <michael.chan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      685ec6a8
  10. 10 7月, 2019 1 次提交
  11. 20 2月, 2019 1 次提交
  12. 07 2月, 2019 4 次提交
  13. 21 12月, 2018 2 次提交
  14. 21 9月, 2018 1 次提交
  15. 07 9月, 2018 1 次提交
  16. 22 8月, 2018 1 次提交
  17. 10 7月, 2018 1 次提交
  18. 25 6月, 2018 1 次提交
  19. 12 4月, 2018 2 次提交
    • S
      bnxt_en: Ignore src port field in decap filter nodes · 479ca3bf
      Sriharsha Basavapatna 提交于
      The driver currently uses src port field (along with other fields) in the
      decap tunnel key, while looking up and adding tunnel nodes. This leads to
      redundant cfa_decap_filter_alloc() requests to the FW and flow-miss in the
      flow engine. Fix this by ignoring the src port field in decap tunnel nodes.
      
      Fixes: f484f678 ("bnxt_en: add hwrm FW cmds for cfa_encap_record and decap_filter")
      Signed-off-by: NSriharsha Basavapatna <sriharsha.basavapatna@broadcom.com>
      Signed-off-by: NMichael Chan <michael.chan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      479ca3bf
    • A
      bnxt_en: do not allow wildcard matches for L2 flows · e85a9be9
      Andy Gospodarek 提交于
      Before this patch the following commands would succeed as far as the
      user was concerned:
      
      $ tc qdisc add dev p1p1 ingress
      $ tc filter add dev p1p1 parent ffff: protocol all \
      	flower skip_sw action drop
      $ tc filter add dev p1p1 parent ffff: protocol ipv4 \
      	flower skip_sw src_mac 00:02:00:00:00:01/44 action drop
      
      The current flow offload infrastructure used does not support wildcard
      matching for ethernet headers, so do not allow the second or third
      commands to succeed.  If a user wants to drop traffic on that interface
      the protocol and MAC addresses need to be specified explicitly:
      
      $ tc qdisc add dev p1p1 ingress
      $ tc filter add dev p1p1 parent ffff: protocol arp \
      	flower skip_sw action drop
      $ tc filter add dev p1p1 parent ffff: protocol ipv4 \
      	flower skip_sw action drop
      ...
      $ tc filter add dev p1p1 parent ffff: protocol ipv4 \
      	flower skip_sw src_mac 00:02:00:00:00:01 action drop
      $ tc filter add dev p1p1 parent ffff: protocol ipv4 \
      	flower skip_sw src_mac 00:02:00:00:00:02 action drop
      ...
      
      There are also checks for VLAN parameters in this patch as other callers
      may wildcard those parameters even if tc does not.  Using different
      flow infrastructure could allow this to work in the future for L2 flows,
      but for now it does not.
      
      Fixes: 2ae7408f ("bnxt_en: bnxt: add TC flower filter offload support")
      Signed-off-by: NAndy Gospodarek <gospo@broadcom.com>
      Signed-off-by: NMichael Chan <michael.chan@broadcom.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e85a9be9
  20. 12 3月, 2018 2 次提交
  21. 26 1月, 2018 1 次提交
  22. 18 1月, 2018 1 次提交
  23. 09 1月, 2018 1 次提交
  24. 11 12月, 2017 1 次提交
    • T
      rhashtable: Change rhashtable_walk_start to return void · 97a6ec4a
      Tom Herbert 提交于
      Most callers of rhashtable_walk_start don't care about a resize event
      which is indicated by a return value of -EAGAIN. So calls to
      rhashtable_walk_start are wrapped wih code to ignore -EAGAIN. Something
      like this is common:
      
             ret = rhashtable_walk_start(rhiter);
             if (ret && ret != -EAGAIN)
                     goto out;
      
      Since zero and -EAGAIN are the only possible return values from the
      function this check is pointless. The condition never evaluates to true.
      
      This patch changes rhashtable_walk_start to return void. This simplifies
      code for the callers that ignore -EAGAIN. For the few cases where the
      caller cares about the resize event, particularly where the table can be
      walked in mulitple parts for netlink or seq file dump, the function
      rhashtable_walk_start_check has been added that returns -EAGAIN on a
      resize event.
      Signed-off-by: NTom Herbert <tom@quantonium.net>
      Acked-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      97a6ec4a
  25. 07 12月, 2017 2 次提交
  26. 03 12月, 2017 2 次提交
  27. 28 10月, 2017 1 次提交
  28. 27 10月, 2017 1 次提交