1. 22 3月, 2016 2 次提交
  2. 10 3月, 2016 1 次提交
    • M
      net/mlx5_core: Introduce forward to next priority action · b3638e1a
      Maor Gottlieb 提交于
      Add support to create flow rule that forward packets
      to the first flow table in the next priority (next priority
      could be the first priority in the next namespace or the
      next priority in the same namespace).
      This feature could be used for DONT_TRAP rules or rules
      that only want to mark the packet with flow tag.
      
      In order to do it optimally, each flow table has list
      of all rules that point to this flow table,
      when a flow table is destroyed/created, we update the list
      head correspondingly.
      
      This kind of rule is created when destination is NULL and
      action is MLX5_FLOW_CONTEXT_ACTION_FWD_NEXT_PRIO.
      Signed-off-by: NMaor Gottlieb <maorg@mellanox.com>
      Reviewed-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NDoug Ledford <dledford@redhat.com>
      b3638e1a
  3. 03 3月, 2016 1 次提交
  4. 02 3月, 2016 2 次提交
  5. 01 3月, 2016 3 次提交
  6. 25 2月, 2016 2 次提交
  7. 17 2月, 2016 1 次提交
    • M
      net/mlx5: Use offset based reserved field names in the IFC header file · b4ff3a36
      Matan Barak 提交于
      mlx5_ifc.h is a header file representing the API and ABI between
      the driver to the firmware and hardware. This file is used from
      both the mlx5_ib and mlx5_core drivers.
      
      Previously, this file used incrementing counter to indicate
      reserved fields, for example:
      
      struct mlx5_ifc_odp_per_transport_service_cap_bits {
              u8         send[0x1];
              u8         receive[0x1];
              u8         write[0x1];
              u8         read[0x1];
              u8         reserved_0[0x1];
              u8         srq_receive[0x1];
              u8         reserved_1[0x1a];
      };
      
      If one developer implements through net-next feature A that uses
      reserved_0, they replace it with featureA and renames reserved_1 to
      reserved_0. In the same kernel cycle, a 2nd developer could implement
      feature B through the rdma tree, that uses reserved_1 and split it to
      featureB and a smaller reserved_1 field. This will cause a conflict
      when the two trees are merged.
      
      The source of this conflict is that the 1st developer changed *all*
      reserved fields.
      
      As Linus suggested, we change the layout of structs to:
      
      struct mlx5_ifc_odp_per_transport_service_cap_bits {
      	u8         send[0x1];
      	u8         receive[0x1];
      	u8         write[0x1];
      	u8         read[0x1];
      	u8         reserved_at_4[0x1];
      	u8         srq_receive[0x1];
      	u8         reserved_at_6[0x1a];
      };
      
      This makes the conflicts much more rare and preserves the locality of
      changes.
      Signed-off-by: NMatan Barak <matanb@mellanox.com>
      Signed-off-by: NAlaa Hleihel <alaa@mellanox.com>
      Reported-by: NLinus Torvalds <torvalds@linux-foundation.org>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      b4ff3a36
  8. 22 1月, 2016 1 次提交
  9. 12 1月, 2016 3 次提交
  10. 06 1月, 2016 1 次提交
  11. 24 12月, 2015 3 次提交
  12. 12 12月, 2015 1 次提交
  13. 04 12月, 2015 8 次提交
  14. 16 11月, 2015 1 次提交
    • T
      net/mlx5e: Added self loopback prevention · 66189961
      Tariq Toukan 提交于
      Prevent outgoing multicast frames from looping back to the RX queue.
      
      By introducing new HW capability self_lb_en_modifiable, which indicates
      the support to modify self_lb_en bit in modify_tir command.
      
      When this capability is set we can prevent TIRs from sending back
      loopback multicast traffic to their own RQs, by "refreshing TIRs" with
      modify_tir command, on every time new channels (SQs/RQs) are created at
      device open.
      This is needed since TIRs are static and only allocated once on driver
      load, and the loopback decision is under their responsibility.
      
      Fixes issues of the kind:
      "IPv6: eth2: IPv6 duplicate address fe80::e61d:2dff:fe5c:f2e9 detected!"
      The issue is seen since the IPv6 solicitations multicast messages are
      loopedback and the network stack thinks they are coming from another host.
      
      Fixes: 5c50368f ("net/mlx5e: Light-weight netdev open/stop")
      Signed-off-by: NTariq Toukan <tariqt@mellanox.com>
      Signed-off-by: NSaeed Mahameed <saeedm@mellanox.com>
      Signed-off-by: NOr Gerlitz <ogerlitz@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      66189961
  15. 07 8月, 2015 2 次提交
  16. 27 7月, 2015 1 次提交
  17. 05 6月, 2015 3 次提交
  18. 31 5月, 2015 1 次提交
  19. 03 4月, 2015 1 次提交
  20. 04 10月, 2014 2 次提交