1. 20 5月, 2006 2 次提交
  2. 13 4月, 2006 11 次提交
  3. 29 3月, 2006 1 次提交
  4. 28 2月, 2006 1 次提交
  5. 08 2月, 2006 1 次提交
  6. 05 2月, 2006 3 次提交
  7. 13 1月, 2006 4 次提交
  8. 11 1月, 2006 1 次提交
  9. 02 12月, 2005 1 次提交
  10. 10 11月, 2005 2 次提交
  11. 07 11月, 2005 2 次提交
  12. 29 10月, 2005 6 次提交
  13. 17 10月, 2005 1 次提交
    • S
      [SCSI] Fix aacraid regression · 7a9366e4
      Salyzyn, Mark 提交于
      Juan was kind enough to linger on site, and work on a production
      machine, to try the parameter to make the system stable. He discovered
      that reducing the maximum transfer size issued to the adapter to 128KB
      stabilized his system. This is related to an earlier change for the
      2.6.13 tree resulting from Martin Drab's testing where the transfer size
      was reduced from 4G to 256KB; we needed to go still further in scaling
      back the request size.
      
      Here is the patch that tames this regression.
      Signed-off-by: NMark Salyzyn <aacraid@adaptec.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      7a9366e4
  14. 15 10月, 2005 1 次提交
  15. 27 9月, 2005 3 次提交
    • M
      [SCSI] aacraid: remove aac_insert_entry · 1640a2c3
      Mark Haverkamp 提交于
      Received from Mark Salyzyn from Adaptec.
      
      High Priority Queues have *never* been used in the entire history of the
      aac based adapters. Associated with this, aac_insert_entry can be
      removed, SavedIrql can be removed & padding variable can be removed.
      With the movement of SavedIrql out & replaced with an automatic variable
      qflags, the locking can be refined somewhat. The sparse warnings did not
      catch the need for byte swapping in the 'dprintk' debugging print
      macros, so fixed this up when this code was moved outside of the now
      refined locking.
      Signed-off-by: NMark Haverkamp <markh@osdl.org>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      1640a2c3
    • M
      [SCSI] aacraid: fib size math fix · 63a70eea
      Mark Haverkamp 提交于
      Received from Mark Salyzyn from Adaptec.
      
      The size of the command packet's scatter gather list maximum size was
      miscalculated in the low range leading to the driver initialization
      limiting the maximum i/o size that could go to the Adapter. There were
      no negative operational side effects resulting from this bad math, only
      a subtle limit in performance of the Adapter at the top end of the
      range.
      Signed-off-by: NMark Haverkamp <markh@osdl.org>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      63a70eea
    • M
      [SCSI] aacraid: initialization timeout · 9203344c
      Mark Haverkamp 提交于
      Received from Mark Salyzyn from Adaptec.
      
      In the rare instances where the adapter, or the motherboard, is
      misbehaving; driver initialization or shutdown becomes problematic. By
      introducing a 3 minute timeout on the first interrupt driven command
      during initialization, or the issuance of the adapter shutdown command
      during driver unload, we can resolve the lockup problems induced by
      common (but rare) hardware misbehaviors.
      
      The timeout during initialization, should it occur, is accompanied by a
      message presented to the console and the logs indicating that the user
      should inspect and resolve problems with interrupt routing.
      Signed-off-by: NMark Haverkamp <markh@osdl.org>
      Signed-off-by: NJames Bottomley <James.Bottomley@SteelEye.com>
      9203344c