1. 21 3月, 2006 1 次提交
    • R
      IB/mad: Simplify SMI by eliminating smi_check_local_dr_smp() · 5e9f71a1
      Ralph Campbell 提交于
      The call to ib_get_agent_port() shouldn't be possible to fail when
      smi_check_local_dr_smp() is called from ib_mad_recv_done_handler().
      When it is called from handle_outgoing_dr_smp(), the device and
      port_num come from mad_agent_priv so I assume the call to
      ib_get_agent_port() shouldn't fail either.  In either case,
      smi_check_local_smp() only uses the mad_agent pointer to check that
      mad_agent->device->process_mad is not NULL.  The device pointer would
      have to be the same as the one passed to smi_check_local_dr_smp()
      since that pointer is used later instead of the one checked in
      smi_check_local_smp().
      Signed-off-by: NHal Rosenstock <halr@voltaire.com>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      5e9f71a1
  2. 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
  3. 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