linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Giridhar Malavali <giridhar.malavali@qlogic.com>
Cc: mdr@sgi.com,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	LinuxSCSI <linux-scsi@vger.kernel.org>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	vasu.dev@intel.com
Subject: Re: qla2xxx: Conditionally disable automatic queue full tracking
Date: Thu, 24 Sep 2009 14:49:22 -0500	[thread overview]
Message-ID: <4ABBCD42.8050604@cs.wisc.edu> (raw)
In-Reply-To: <5355D915-9CAE-41CD-846B-F816FE914E1B@qlogic.com>

Giridhar Malavali wrote:
> Hi Michael/James,
> 
>     Patches were submitted to move queue ramp up/down code recently to 
> scsi mid layer. With this change, I don't see a need for a module 
> parameter to disable queuefull tracking  in qla2xxx driver. Andrew, 
> mentioned that this got introduced to avoid wobbling behavior on the 
> wire due to queue depth modifications. Just wanted to check whether the 
> same need to be done in scsi mid layer too.
> 

I think so. I believe Michael Reed had a valid reason for it, and I do 
not see why we would not hit a similar problem with other drivers.

      parent reply	other threads:[~2009-09-24 19:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 23:59 qla2xxx: Conditionally disable automatic queue full tracking Giridhar Malavali
2009-09-24 14:42 ` Michael Reed
2009-09-24 17:05   ` Giridhar Malavali
2009-09-24 19:15     ` Michael Reed
2009-09-24 20:55       ` Giridhar Malavali
2009-09-24 21:02         ` Michael Reed
2009-09-30  1:34           ` Giridhar Malavali
2009-09-30 13:08             ` Michael Reed
2009-09-30 13:43               ` Michael Reed
2009-09-30 18:23             ` Mike Christie
2009-10-02  0:19               ` Michael Reed
2009-10-02 17:17                 ` James Smart
2009-10-06 17:17                   ` Michael Reed
2009-09-24 19:49 ` Mike Christie [this message]

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=4ABBCD42.8050604@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=giridhar.malavali@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mdr@sgi.com \
    --cc=vasu.dev@intel.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;
as well as URLs for NNTP newsgroup(s).