From: James Bottomley <James.Bottomley@SteelEye.com>
To: Sumant Patro <sumant.patro@lsi.com>
Cc: akpm@osdl.org, linux-scsi@vger.kernel.org, neela.kolli@lsi.com,
bo.yang@lsi.com
Subject: Re: [PATCH] scsi: megaraid_sas - intercepts cmd timeout and throttle io
Date: Thu, 10 May 2007 14:23:45 -0500 [thread overview]
Message-ID: <1178825025.3712.11.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1178805687.4681.7.camel@dumbo>
On Thu, 2007-05-10 at 07:01 -0700, Sumant Patro wrote:
> eh_timed_out call back (megasas_reset_timer) is used to throttle io to the adapter
> when it is called the first time for a scmd.
> The MEGASAS_FW_BUSY flag is set and can_queue reduced to 16. The can_queue is restored
> from completion routine in following two conditions : 5 seconds has elapsed and the # of
> outstanding cmds in FW is < 17.
> Also removed reserved fields from struct megasas_instance.
And the rest of the comments?
This is the cut out of all the ones I made, I think:
> > +static enum
> > +scsi_eh_timer_return megasas_reset_timer(struct scsi_cmnd *scmd)
> > +{
> > + struct megasas_cmd *cmd = (struct megasas_cmd *)scmd->SCp.ptr;
> > + struct megasas_instance *instance;
> > + unsigned long flags;
> > +
> > + if (cmd) {
>
> I don't believe we can ever get a command timeout with no command, can
> we?
>
> > + if (time_after(jiffies, scmd->jiffies_at_alloc + 170 *
> HZ))
> > + return EH_NOT_HANDLED;
>
> This 170s is a bit arbitrary ... surely you want it to be related to a
> multiple of scmd->timeout_per_command?
> > + if (!(instance->flag & MEGASAS_FW_BUSY)) {
> > + /* FW is busy, throttle IO */
> > + spin_lock_irqsave(&instance->throttle_io_lock,
> flags);
> > +
> > + instance->host->can_queue = 16;
>
> can_queue is protected by the host lock ... I think you need to dump
> the
> throttle_io_lock and simply use the host lock for all of this.
> > - if (cmd->scmd) {
> > + if (cmd->scmd)
> > cmd->scmd->SCp.ptr = (char *)0;
>
> That's NULL, ordinarily ...
James
next prev parent reply other threads:[~2007-05-10 19:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 14:01 [PATCH] scsi: megaraid_sas - intercepts cmd timeout and throttle io Sumant Patro
2007-05-10 19:23 ` James Bottomley [this message]
2007-05-10 19:57 ` [PATCH] scsi: megaraid_sas - intercepts cmd timeout andthrottle io Patro, Sumant
-- strict thread matches above, loose matches on Subject: below --
2007-05-17 12:47 [PATCH] scsi: megaraid_sas - intercepts cmd timeout and throttle io Sumant Patro
2007-03-28 17:43 Sumant Patro
2007-04-26 17:39 ` James Bottomley
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=1178825025.3712.11.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bo.yang@lsi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=neela.kolli@lsi.com \
--cc=sumant.patro@lsi.com \
/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