1. 12 Jan, 2006 1 commit
  2. 13 Dec, 2005 5 commits
    • James.Smart@Emulex.Com's avatar
    • James.Smart@Emulex.Com's avatar
      [SCSI] lpfc 8.1.1 : Add polled-mode support · 875fbdfe
      James.Smart@Emulex.Com authored
      - Add functionality to run in polled mode only. Includes run time
        attribute to enable mode.
      - Enable runtime writable hba settings for coallescing and delay parameters
      Customers have requested a mode in the driver to run strictly polled.
      This is generally to support an environment where the server is extremely
      loaded and is looking to reclaim some cpu cycles from adapter interrupt
      This patch adds a new "poll" attribute, and the following behavior:
      if value is 0 (default):
        The driver uses the normal method for i/o completion. It uses the
        firmware feature of interrupt coalesing. The firmware allows a
        minimum number of i/o completions before an interrupt, or a maximum
        time delay between interrupts.  By default, the driver sets these
        to no delay (disabled) or 1 i/o - meaning coalescing is disabled.
        Attributes were provided to change the coalescing values, but it was
        a module-load time only and global across all adapters.
        This patch allows them to be writable on a per-adapter basis.
      if value is 1 :
        Interrupts are left enabled, expecting that the user has tuned the
        interrupt coalescing values. When this setting is enabled, the driver
        will attempt to service completed i/o whenever new i/o is submitted
        to the adapter. If the coalescing values are large, and the i/o
        generation rate steady, an interrupt will be avoided by servicing
        completed i/o prior to the coalescing thresholds kicking in. However,
        if the i/o completion load is high enough or i/o generation slow, the
        coalescion values will ensure that completed i/o is serviced in a timely
      if value is 3 :
        Turns off FCP i/o interrupts altogether. The coalescing values now have
        no effect. A new attribute "poll_tmo" (default 10ms) exists to set
        the polling interval for i/o completion. When this setting is enabled,
        the driver will attempt to service completed i/o and restart the
        interval timer whenever new i/o is submitted. This behavior allows for
        servicing of completed i/o sooner than the interval timer, but ensures
        that if no i/o is being issued, then the interval timer will kick in
        to service the outstanding i/o.
      Signed-off-by: default avatarJames Smart <James.Smart@emulex.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James.Smart@Emulex.Com's avatar
      [SCSI] lpfc 8.1.1 : Fixes to error handlers · 6175c02a
      James.Smart@Emulex.Com authored
      - Release task management command before counting outstanding commands.
        TMF was being erroneously counted as an active outstanding command.
      - Serialize EH calls and block requests when EH function is running.
      Signed-off-by: default avatarJames Smart <James.Smart@emulex.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James.Smart@Emulex.Com's avatar
      [SCSI] lpfc 8.1.1 : Remove locking wrappers around error handlers · 63c59c3b
      James.Smart@Emulex.Com authored
      Remove locking wrappers around error handlers. Wrappers were added in
      early 2.6.13 api change
      Signed-off-by: default avatarJames Smart <James.Smart@emulex.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
    • James.Smart@Emulex.Com's avatar
      [SCSI] lpfc 8.1.1: Miscellaneous Cleanups · 1de933f3
      James.Smart@Emulex.Com authored
      Miscellaneous Cleanups:
      - Remove ProgType READ_REV mailbox command value check in lpfc_config_port_prep.
      - Convert simple printk to an lpfc_printf_log in queuecommand.
      - Modify lpfc_abort_handler message 0749 to display more accurate text and data.
      - Minor style cleanup: fix 3 long lines in lpfc_hw.h
      Signed-off-by: default avatarJames Smart <James.Smart@emulex.com>
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  3. 07 Nov, 2005 1 commit
  4. 29 Oct, 2005 4 commits
  5. 28 Oct, 2005 1 commit
    • James.Smart@Emulex.Com's avatar
      [SCSI] update fc_transport for removal of block/unblock functions · 19a7b4ae
      James.Smart@Emulex.Com authored
      We recently went back to implement a board reset. When we perform the
      reset, we wanted to tear down the internal data structures and rebuild
      them. Unfortunately, when it came to the rport structure, things were
      odd. If we deleted them, the scsi targets and sdevs would be
      torn down. Not a good thing for a temporary reset. We could block the
      rports, but we either maintain the internal structures to keep the
      rport reference (perhaps even replicating what's in the transport),
      or we have to fatten the fc transport with new search routines to find
      the rport (and deal with a case of a dangling rport that the driver
      It dawned on me that we had actually reached this state incorrectly.
      When the fc transport first started, we did the block/unblock first, then
      added the rport interface. The purpose of block/unblock is to hide the
      temporary disappearance of the rport (e.g. being deleted, then readded).
      Why are we making the driver do the block/unblock ? We should be making
      the transport have only an rport add/delete, and the let the transport
      handle the block/unblock.
      So... This patch removes the existing fc_remote_port_block/unblock
      functions. It moves the block/unblock functionality into the
      fc_remote_port_add/delete functions.  Updates for the lpfc driver are
      included. Qlogic driver updates are also enclosed, thanks to the
      contributions of Andrew Vasquez. [Note: the qla2xxx changes are
      relative to the scsi-misc-2.6 tree as of this morning - which does
      not include the recent patches sent by Andrew]. The zfcp driver does
      not use the block/unblock functions.
      One last comment: The resulting behavior feels very clean. The LLDD is
      concerned only with add/delete, which corresponds to the physical
      disappearance.  However, the fact that the scsi target and sdevs are
      not immediately torn down after the LLDD calls delete causes an
      interesting scenario... the midlayer can call the xxx_slave_alloc and
      xxx_queuecommand functions with a sdev that is at the location the
      rport used to be. The driver must validate the device exists when it
      first enters these functions. In thinking about it, this has always
      been the case for the LLDD and these routines. The existing drivers
      already check for existence. However, this highlights that simple
      validation via data structure dereferencing needs to be watched.
      To deal with this, a new transport function, fc_remote_port_chkready()
      was created that LLDDs should call when they first enter these two
      routines. It validates the rport state, and returns a scsi result
      which could be returned. In addition to solving the above, it also
      creates consistent behavior from the LLDD's when the block and deletes
      are occuring.
      Rejections fixed up and
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@SteelEye.com>
  6. 12 Aug, 2005 4 commits
  7. 02 Jul, 2005 4 commits
  8. 17 Jun, 2005 3 commits
  9. 18 Apr, 2005 1 commit