1. 05 2月, 2007 4 次提交
    • H
      IB/ehca: Remove use of do_mmap() · 4c34bdf5
      Hoang-Nam Nguyen 提交于
      This patch removes do_mmap() from ehca:
       - Call remap_pfn_range() for hardware register block
       - Use vm_insert_page() to register memory allocated for completion
         queues and queue pairs
       - The actual mmap() call/trigger is now controlled by user space,
         ie. libehca
      Signed-off-by: NHoang-Nam Nguyen <hnguyen@de.ibm.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      4c34bdf5
    • S
      RDMA/addr: Handle ethernet neighbour updates during route resolution · 1f126670
      Steve Wise 提交于
      The iWARP connection manager uses the ib_addr services to do route
      resolution (neighbour discovery in the IP world).  The ib_addr
      netevent callback routine, however, currently only acts on InfiniBand
      neighbour updates.  It needs to act on ethernet neighbour updates as
      well.
      
      This patch just removes filtering on device type altogether and will
      trigger on any neighour updates where the nud_type is valid.  This
      simplifies the code some.
      Signed-off-by: NSteve Wise <swise@opengridcomputing.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      1f126670
    • I
      IB/srp: Don't wait for response when QP is in error state. · 1033ff67
      Ishai Rabinovitz 提交于
      When there is a call to send_tsk_mgmt SRP posts a send and waits for 5
      seconds to get a response.
      
      When the QP is in the error state it is obvious that there will be no
      response so it is quite useless to wait.  In fact, the timeout causes
      SRP to wait a long time to reconnect when a QP error occurs. (Each
      abort and each reset_device calls send_tsk_mgmt, which waits for the
      timeout).  The following patch solves this problem by identifying the
      failure and returning an immediate error code.
      Signed-off-by: NIshai Rabinovitz <ishai@mellanox.co.il>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      1033ff67
    • 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 次提交