1. 05 2月, 2007 1 次提交
    • M
      IB: Return qp pointer as part of ib_wc · 062dbb69
      Michael S. Tsirkin 提交于
      struct ib_wc currently only includes the local QP number: this matches
      the IB spec, but seems mostly useless. The following patch replaces
      this with the pointer to qp itself, and updates all low level drivers
      and all users.
      
      This has the following advantages:
      - Ability to get a per-qp context through wc->qp->qp_context
      - Existing drivers already have the qp pointer ready in poll cq, so
        this change actually saves a tiny bit (extra memory read) on data path
        (for ehca it would actually be expensive to find the QP pointer when
        polling a CQ, but ehca does not support SRQ so we can leave wc->qp as
        NULL for ehca)
      - Users that need the QP number can still get it through wc->qp->qp_num
      
      Use case:
      
      In IPoIB connected mode code, I have a common CQ shared by multiple
      QPs.  To track connection usage, I need a way to get at some per-QP
      context upon the completion, and I would like to avoid allocating
      context object per work request just to stick a QP pointer into it.
      With this code, I can just use wc->qp->qp_context.
      Signed-off-by: NMichael S. Tsirkin <mst@mellanox.co.il>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      062dbb69
  2. 23 1月, 2007 3 次提交
  3. 10 1月, 2007 2 次提交
  4. 08 1月, 2007 5 次提交
  5. 05 1月, 2007 1 次提交
    • M
      IB/mthca: Fix off-by-one in FMR handling on memfree · 46707e96
      Michael S. Tsirkin 提交于
      mthca_table_find() will return the wrong address when the table entry
      being searched for is exactly at the beginning of a sglist entry
      (other than the first), because it uses >= when it should use >.
      
      Example: assume we have 2 entries in scatterlist, 4K each, offset is
      4K.  The current code will return first entry + 4K when we really want
      the second entry.
      
      In particular this means mapping an FMR on a memfree HCA may end up
      writing the page table into the wrong place, leading to memory
      corruption and also causing the HCA to use an incorrect address
      translation table.
      Signed-off-by: NMichael S. Tsirkin <mst@mellanox.co.il>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      46707e96
  6. 31 12月, 2006 1 次提交
  7. 16 12月, 2006 3 次提交
  8. 13 12月, 2006 16 次提交
  9. 09 12月, 2006 2 次提交
  10. 08 12月, 2006 2 次提交
  11. 04 12月, 2006 1 次提交
  12. 30 11月, 2006 3 次提交