1. 15 7月, 2008 1 次提交
  2. 10 7月, 2007 1 次提交
  3. 11 2月, 2007 1 次提交
    • M
      IPoIB: Connected mode experimental support · 839fcaba
      Michael S. Tsirkin 提交于
      The following patch adds experimental support for IPoIB connected
      mode, as defined by the draft from the IETF ipoib working group.  The
      idea is to increase performance by increasing the MTU from the maximum
      of 2K (theoretically 4K) supported by IPoIB on top of UD.  With this
      code, I'm able to get 800MByte/sec or more with netperf without
      options on a Mellanox 4x back-to-back DDR system.
      
      Some notes on code:
      1. SRQ is used for scalability to large cluster sizes
      2. Only RC connections are used (UC does not support SRQ now)
      3. Retry count is set to 0 since spec draft warns against retries
      4. Each connection is used for data transfers in only 1 direction, so
         each connection is either active(TX) or passive (RX).  2 sides that
         want to communicate create 2 connections.
      5. Each active (TX) connection has a separate CQ for send completions -
         this keeps the code simple without CQ resize and other tricks
      6. To detect stale passive side connections (where the remote side is
         down), we keep an LRU list of passive connections (updated once per
         second per connection) and destroy a connection after it has been
         unused for several seconds. The LRU rule makes it possible to avoid
         scanning connections that have recently been active.
      Signed-off-by: NMichael S. Tsirkin <mst@mellanox.co.il>
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      839fcaba
  4. 04 10月, 2006 1 次提交
  5. 04 8月, 2006 1 次提交
  6. 03 4月, 2006 1 次提交
    • R
      IPoIB: Always build debugging code unless CONFIG_EMBEDDED=y · f5545d24
      Roland Dreier 提交于
      Don't allow CONFIG_INFINIBAND_IPOIB_DEBUG to be disabled unless
      CONFIG_EMBEDDED is selected.  We want users (and especially distros)
      to have this turned on unless they really need to save space, because
      by the time we want debugging output, it's usually too late to rebuild
      a kernel.  The debugging output can be controlled at runtime via the
      debug_level module parameter in sysfs.
      Signed-off-by: NRoland Dreier <rolandd@cisco.com>
      f5545d24
  7. 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