1. 30 Aug, 2015 4 commits
  2. 05 May, 2015 1 commit
    • David Ahern's avatar
      IB/core: Fix unaligned accesses · 0d0f738f
      David Ahern authored
      Addresses the following kernel logs seen during boot of sparc systems:
      
      Kernel unaligned access at TPC[103bce50] cm_find_listen+0x34/0xf8 [ib_cm]
      Kernel unaligned access at TPC[103bce50] cm_find_listen+0x34/0xf8 [ib_cm]
      Kernel unaligned access at TPC[103bce50] cm_find_listen+0x34/0xf8 [ib_cm]
      Kernel unaligned access at TPC[103bce50] cm_find_listen+0x34/0xf8 [ib_cm]
      Kernel unaligned access at TPC[103bce50] cm_find_listen+0x34/0xf8 [ib_cm]
      Signed-off-by: default avatarDavid Ahern <david.ahern@oracle.com>
      Signed-off-by: default avatarDoug Ledford <dledford@redhat.com>
      0d0f738f
  3. 01 Apr, 2014 1 commit
  4. 14 Jan, 2014 1 commit
    • Matan Barak's avatar
      IB/core: Ethernet L2 attributes in verbs/cm structures · dd5f03be
      Matan Barak authored
      This patch add the support for Ethernet L2 attributes in the
      verbs/cm/cma structures.
      
      When dealing with L2 Ethernet, we should use smac, dmac, vlan ID and priority
      in a similar manner that the IB L2 (and the L4 PKEY) attributes are used.
      
      Thus, those attributes were added to the following structures:
      
      * ib_ah_attr - added dmac
      * ib_qp_attr - added smac and vlan_id, (sl remains vlan priority)
      * ib_wc - added smac, vlan_id
      * ib_sa_path_rec - added smac, dmac, vlan_id
      * cm_av - added smac and vlan_id
      
      For the path record structure, extra care was taken to avoid the new
      fields when packing it into wire format, so we don't break the IB CM
      and SA wire protocol.
      
      On the active side, the CM fills. its internal structures from the
      path provided by the ULP.  We add there taking the ETH L2 attributes
      and placing them into the CM Address Handle (struct cm_av).
      
      On the passive side, the CM fills its internal structures from the WC
      associated with the REQ message.  We add there taking the ETH L2
      attributes from the WC.
      
      When the HW driver provides the required ETH L2 attributes in the WC,
      they set the IB_WC_WITH_SMAC and IB_WC_WITH_VLAN flags. The IB core
      code checks for the presence of these flags, and in their absence does
      address resolution from the ib_init_ah_from_wc() helper function.
      
      ib_modify_qp_is_ok is also updated to consider the link layer. Some
      parameters are mandatory for Ethernet link layer, while they are
      irrelevant for IB.  Vendor drivers are modified to support the new
      function signature.
      Signed-off-by: default avatarMatan Barak <matanb@mellanox.com>
      Signed-off-by: default avatarOr Gerlitz <ogerlitz@mellanox.com>
      Signed-off-by: default avatarRoland Dreier <roland@purestorage.com>
      dd5f03be
  5. 08 Jul, 2012 1 commit
  6. 04 Jan, 2012 1 commit
  7. 21 Sep, 2009 1 commit
  8. 17 Jan, 2009 1 commit
  9. 15 Jul, 2008 1 commit
  10. 09 Oct, 2007 1 commit
    • Sean Hefty's avatar
      IB/cm: Modify interface to send MRAs in response to duplicate messages · de98b693
      Sean Hefty authored
      The IB CM provides a message received acknowledged (MRA) message that
      can be sent to indicate that a REQ or REP message has been received, but
      will require more time to process than the timeout specified by those
      messages.  In many cases, the application may not know how long it will
      take to respond to a CM message, but the majority of the time, it will
      usually respond before a retry has been sent.  Rather than sending an
      MRA in response to all messages just to handle the case where a longer
      timeout is needed, it is more efficient to queue the MRA for sending in
      case a duplicate message is received.
      
      This avoids sending an MRA when it is not needed, but limits the number
      of times that a REQ or REP will be resent.  It also provides for a
      simpler implementation than generating the MRA based on a timer event.
      (That is, trying to send the MRA after receiving the first REQ or REP if
      a response has not been generated, so that it is received at the remote
      side before a duplicate REQ or REP has been received)
      Signed-off-by: default avatarSean Hefty <sean.hefty@intel.com>
      Signed-off-by: default avatarRoland Dreier <rolandd@cisco.com>
      de98b693
  11. 10 Jul, 2007 1 commit
  12. 29 Nov, 2006 1 commit
    • Sean Hefty's avatar
      IB/cm: Fix automatic path migration support · e1444b5a
      Sean Hefty authored
      The ib_cm_establish() function is replaced with a more generic
      ib_cm_notify().  This routine is used to notify the CM that failover
      has occurred, so that future CM messages (LAP, DREQ) reach the remote
      CM.  (Currently, we continue to use the original path)  This bumps the
      userspace CM ABI.
      
      New alternate path information is captured when a LAP message is sent
      or received.  This allows QP attributes to be initialized for the user
      when a new path is loaded after failover occurs.
      Signed-off-by: default avatarSean Hefty <sean.hefty@intel.com>
      Signed-off-by: default avatarRoland Dreier <rolandd@cisco.com>
      e1444b5a
  13. 17 Jun, 2006 2 commits
  14. 17 Oct, 2005 1 commit
  15. 09 Sep, 2005 1 commit
  16. 26 Aug, 2005 2 commits
  17. 28 Jul, 2005 1 commit
  18. 27 Jul, 2005 1 commit