1. 26 10月, 2005 1 次提交
    • S
      [IB] Fix MAD layer DMA mappings to avoid touching data buffer once mapped · 34816ad9
      Sean Hefty 提交于
      The MAD layer was violating the DMA API by touching data buffers used
      for sends after the DMA mapping was done.  This causes problems on
      non-cache-coherent architectures, because the device doing DMA won't
      see updates to the payload buffers that exist only in the CPU cache.
      
      Fix this by having all MAD consumers use ib_create_send_mad() to
      allocate their send buffers, and moving the DMA mapping into the MAD
      layer so it can be done just before calling send (and after any
      modifications of the send buffer by the MAD layer).
      
      Tested on a non-cache-coherent PowerPC 440SPe system.
      Signed-off-by: NSean Hefty <sean.hefty@intel.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      34816ad9
  2. 25 10月, 2005 1 次提交
  3. 18 10月, 2005 1 次提交
  4. 09 10月, 2005 1 次提交
  5. 10 9月, 2005 1 次提交
  6. 08 9月, 2005 1 次提交
  7. 27 8月, 2005 2 次提交
  8. 28 7月, 2005 5 次提交
  9. 28 6月, 2005 1 次提交
  10. 26 5月, 2005 1 次提交
    • R
      [PATCH] IB: allow NULL sa_query callbacks · e4f50f00
      Roland Dreier 提交于
      Check if a client passes a NULL callback into an SA query, and if so, never
      call back.  This fixes an oops if someone unloads ib_ipoib and ib_sa in
      rapid succession.  ib_ipoib does an MCMember delete with a NULL callback
      and 0 timeout on unload, which is usually fine since the delete completes
      successfully.  However, if ib_sa is unloaded immediately afterwards, the
      delete will be canceled and ib_sa will try to call the (now already
      unloaded) ib_ipoib module back with the cancel completion, which triggers
      the oops.
      Signed-off-by: NRoland Dreier <roland@topspin.com>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      e4f50f00
  11. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4