An error occurred fetching the project authors.
  1. 04 Aug, 2007 1 commit
  2. 27 Jul, 2007 1 commit
  3. 24 Jul, 2007 1 commit
  4. 23 Jul, 2007 2 commits
  5. 20 Jun, 2007 2 commits
  6. 17 Jun, 2007 1 commit
  7. 01 Jun, 2007 2 commits
  8. 22 May, 2007 1 commit
    • Salyzyn, Mark's avatar
      [SCSI] aacraid: add support for FUA · 9d399cc7
      Salyzyn, Mark authored
      Back in the beginning of last year we disabled mode page 8 and mode page
      3f requests through device quirk bits instead of enhancing the driver to
      respond to these mode pages because there was no apparent added value.
      
      The Firmware that supports the new communication commands supports the
      ability to force a write around of the adapter cache on a command by
      command basis. In the attached patch we enable mode page 8 and 3f and
      spoof the results as needed in order to *convince* the layers above to
      submit writes with the FUA (Force Unit Attention) bit set if the file
      system or application requires it, if the Firmware supports the write
      through, or instead to submit a SYNCHRONIZE_CACHE if the Firmware does
      not. The added value here is for file systems that benefit from this
      functionality and for clustering or redundancy scenarios.
      
      Caveats: By convince, we are responding with a minimal short 3 byte
      content mode page 8, with only the data the SCSI layer needs and that we
      can fill confidently. Applications that require the customarily larger
      mode page 8 results may be confused by this(?). The FUA, or the
      SYNCHRONIZE_CACHE only affect the cache on the controller. Our firmware
      by default ensure that the underlying physical drives of the array have
      their cache turned off so normally this is not a problem.
      
      This attached patch is against current scsi-misc-2.6 and was unit tested
      on RHEL5. Since this is a feature enhancement, it should not be
      considered for any current stabilization efforts.
      Signed-off-by: default avatarMark Salyzyn <aacraid@adaptec.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      9d399cc7
  9. 01 Apr, 2007 1 commit
  10. 21 Mar, 2007 1 commit
    • Salyzyn, Mark's avatar
      [SCSI] aacraid: cleanup and version stamp driver · 802ae2f0
      Salyzyn, Mark authored
      There is some residual cleanup of the last series of patches and the
      need to bump the revision number to draw the line in the sand.
      
      The cmd->SCp.phase is set in the aac_valid_context routine, then set
      again to the same value following it's return. The cmd->scsi_done is set
      twice in the aac_queuecommand routine. Free up the scsidev FILO in
      aac_probe_container as it is not needed further down the function in any
      case. Improve the efficiency of the abort handler kernel print
      parameters. Bump revision number of driver to approximate the equivalent
      in the Adaptec supplied version.
      Signed-off-by: default avatarMark Salyzyn <aacraid@adaptec.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      802ae2f0
  11. 20 Mar, 2007 1 commit
    • Mark Haverkamp's avatar
      [SCSI] aacraid: Improved error handling · 03d44337
      Mark Haverkamp authored
      Received from Mark Salyzyn,
      
      This set of fixes improve error handling stability of the driver. A popular
      manifestation of the problems is an NULL pointer reference in the interrupt
      handler when referencing portions of the scsi command context, or in the
      scsi_done handling when an offlined device is referenced.
      
      The aacraid driver currently does not get notification of orphaned command
      completions due to devices going offline. The driver also fails to handle the
      commands that are finished by the error handler, and thus can complete again
      later at the hands of the adapter causing situations of completion of an
      invalid scsi command context. Test Unit Ready calls abort assuming that the
      abort was successful, but are not, and thus when the interrupt from the adapter
      occurs, they reference invalid command contexts. We add in a TIMED_OUT flag to
      inform the aacraid FIB context that the interrupt service should merely release
      the driver resources and not complete the command up. We take advantage of this
      with the abort handler as well for select abortable commands. And we detect and
      react if a command that can not be aborted is currently still outstanding to
      the controller when reissued by the retry mechanism.
      Signed-off-by: default avatarMark Haverkamp <markh@linux-foundation.org>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      03d44337
  12. 12 Feb, 2007 1 commit
  13. 27 Jan, 2007 2 commits
  14. 06 Jan, 2007 1 commit
  15. 24 Sep, 2006 2 commits
    • Mark Haverkamp's avatar
      [SCSI] aacraid: merge rx and rkt code · 76a7f8fd
      Mark Haverkamp authored
      Received from Mark Salyzyn:
      
      The only real difference between the rkt and rx platform modules is the
      offset of the message registers. This patch recognizes this similarity
      and simplifies the driver to reduce it's code footprint and to improve
      maintainability by reducing the code duplication.
      
      Visibly, the 'rkt.c' portion of this patch looks more complicated than
      it really is. View it as retaining the rkt-only specifics of the
      interface.
      Signed-off-by: default avatarMark Haverkamp <markh@osdl.org>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      76a7f8fd
    • Mark Haverkamp's avatar
      [SCSI] aacraid: expose physical devices · 653ba58d
      Mark Haverkamp authored
      Received from Mark Salyzyn:
      
      I am placing this functionality into an insmod parameter. Normally the physical
      components are exported to sg, and are blocked from showing up in sd.
      
      Note that the pass-through I/O path via the driver through the Firmware to the
      physical disks is not an optimized path, the card is designed for Hardware
      RAID, elevator sorting and caching. This should not be used as a means for
      utilizing the aacraid based controllers as a generic scsi/SATA/SAS controller,
      performance should suck by a few percentage points, any RAID meta-data on the
      drives will confuse the controller about who owns the drives and there is a
      high risk of destroying content in both directions. Unreliable and for
      experimentation or strange controlled circumstances only.
      Signed-off-by: default avatarMark Haverkamp <markh@osdl.org>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
      653ba58d
  16. 19 Aug, 2006 2 commits
  17. 20 Jun, 2006 1 commit
  18. 12 Jun, 2006 1 commit
  19. 20 May, 2006 1 commit
  20. 13 Apr, 2006 8 commits
  21. 28 Mar, 2006 1 commit
  22. 28 Feb, 2006 1 commit
  23. 04 Feb, 2006 3 commits
  24. 12 Jan, 2006 2 commits