public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Alexis Bruemmer <alexisb@us.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Raoul Bhatia [IPAX]" <r.bhatia@ipax.at>, linux-scsi@vger.kernel.org
Subject: Re: aic94xx driver woes continued
Date: Thu, 20 Mar 2008 15:18:47 -0700	[thread overview]
Message-ID: <1206051527.19541.14.camel@alexis> (raw)
In-Reply-To: <1206047850.3038.52.camel@localhost.localdomain>


On Thu, 2008-03-20 at 16:17 -0500, James Bottomley wrote:
> On Thu, 2008-03-20 at 22:08 +0100, Raoul Bhatia [IPAX] wrote:
> > hi james,
> > 
> > James Bottomley wrote:
> >  > A work around might be to lower the queue depth to say 4 or 8 and up the
> >  > retries (this latter can only be done by altering the SD_MAX_RETRIES
> >  > parameter in include/scsi/sd.h and recompiling).
> > 
> > any suggestions for these parameters:
> > 
> > include/scsi/sd.h:
> >  > #define SD_TIMEOUT              (30 * HZ)
> >  > #define SD_MOD_TIMEOUT          (75 * HZ)
> >  >
> >  > #define SD_MAX_RETRIES          5
> >  > #define SD_PASSTHROUGH_RETRIES  1
> > 
> > shall i alter the timeouts?
> 
> The timeouts can be altered on the fly
> at /sys/class/scsi_device/<device>/device/timeout
> 
> but I'd leave them as is for now ... it wasn't the timeouts that fired.
> 
> > what is a good value for the retries? time it by 2? by 5? by 10?
> 
> I'd up the retries to say 15 and see if that works.
> 
> > moreover, where can i lower the queue?
> 
> echo <new depth> > /sys/class/scsi_device/<device>/device/queue_depth

We have played a lot with the queue depth on this controller.  So far
the best we have done is extended the time before an end device is
eventually dropped.  I am very curious to see what happens in Raoul's
test case.


> 
> James
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2008-03-20 22:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 18:43 aic94xx driver woes continued Raoul Bhatia [IPAX]
2008-03-20 19:01 ` James Bottomley
2008-03-20 19:14   ` Raoul Bhatia [IPAX]
2008-03-29 22:36     ` Luben Tuikov
2008-03-20 19:15   ` Raoul Bhatia [IPAX]
2008-03-20 19:18     ` Raoul Bhatia [IPAX]
2008-03-20 19:57     ` James Bottomley
2008-03-20 20:21       ` Raoul Bhatia [IPAX]
2008-03-20 21:08       ` Raoul Bhatia [IPAX]
2008-03-20 21:17         ` James Bottomley
2008-03-20 22:18           ` Alexis Bruemmer [this message]
2008-03-26 14:34             ` Raoul Bhatia [IPAX]
2008-03-29 22:39       ` Luben Tuikov
2008-03-29 22:33   ` Luben Tuikov
2008-03-31 20:23     ` Raoul Bhatia [IPAX]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1206051527.19541.14.camel@alexis \
    --to=alexisb@us.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=r.bhatia@ipax.at \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox