1. 25 2月, 2010 2 次提交
    • A
      IB/uverbs: Remove dev_table · 2a72f212
      Alexander Chiang 提交于
      dev_table's raison d'etre was to associate an inode back to a struct
      ib_uverbs_device.
      
      However, now that we've converted ib_uverbs_device to contain an
      embedded cdev (instead of a *cdev), we can use the container_of()
      macro and cast back to the containing device.
      
      There's no longer any need for dev_table, so get rid of it.
      Signed-off-by: NAlex Chiang <achiang@hp.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      2a72f212
    • A
      IB/uverbs: Convert *cdev to cdev in struct ib_uverbs_device · 055422dd
      Alexander Chiang 提交于
      Instead of storing a pointer to a cdev, embed the entire struct cdev.
      
      This change allows us to use the container_of() macro in
      ib_uverbs_open() in a future patch.
      
      This change increases the size of struct ib_uverbs_device to 168 bytes
      across 3 cachelines from 80 bytes in 2 cachelines.  However, we
      rearrange the members so that everything fits into the first cacheline
      except for the struct cdev. Finally, we don't touch the cdev in any
      fastpaths, so this change shouldn't negatively affect performance.
      Signed-off-by: NAlex Chiang <achiang@hp.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      055422dd
  2. 11 2月, 2010 1 次提交
    • S
      RDMA/cm: Revert association of an RDMA device when binding to loopback · 8523c048
      Sean Hefty 提交于
      Revert the following change from commit 6f8372b6 ("RDMA/cm: fix
      loopback address support")
      
         The defined behavior of rdma_bind_addr is to associate an RDMA
         device with an rdma_cm_id, as long as the user specified a non-
         zero address.  (ie they weren't just trying to reserve a port)
         Currently, if the loopback address is passed to rdma_bind_addr,
         no device is associated with the rdma_cm_id.  Fix this.
      
      It turns out that important apps such as Open MPI depend on
      rdma_bind_addr() NOT associating any RDMA device when binding to a
      loopback address.  Open MPI is being updated to deal with this, but at
      least until a new Open MPI release is available, maintain the previous
      behavior: allow rdma_bind_addr() to succeed, but do not bind to a
      device.
      Signed-off-by: NSean Hefty <sean.hefty@intel.com>
      Acked-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      8523c048
  3. 27 1月, 2010 1 次提交
  4. 07 1月, 2010 3 次提交
  5. 23 12月, 2009 5 次提交
  6. 17 12月, 2009 1 次提交
  7. 16 12月, 2009 1 次提交
  8. 10 12月, 2009 26 次提交