From: Michael Reed <mdr@sgi.com>
To: Giridhar Malavali <giridhar.malavali@qlogic.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Mike Christie <michaelc@cs.wisc.edu>,
LinuxSCSI <linux-scsi@vger.kernel.org>,
Andrew Vasquez <andrew.vasquez@qlogic.com>,
"vasu.dev@intel.com" <vasu.dev@intel.com>
Subject: Re: qla2xxx: Conditionally disable automatic queue full tracking
Date: Thu, 24 Sep 2009 14:15:11 -0500 [thread overview]
Message-ID: <4ABBC53F.9090203@sgi.com> (raw)
In-Reply-To: <67E59C8B-0E12-44EA-983C-38634993DF5A@qlogic.com>
To answer your query, yes. Ultimately, I believe the ml should be
modified to view a user space modification to a lun's queue depth
as an upper bound. I don't care, much, whether the system dynamically
adjusts the queue depth or leaves it alone as long as it honors the
value programmed via user space.
Are you volunteering to do the work? :) How can I help?
Thanks,
Mike
Giridhar Malavali wrote:
> Hi Michael,
>
> Here are the patches..
>
> http://marc.info/?a=119828370000006&r=1&w=2 .
> http://marc.info/?l=linux-scsi&m=125201657106722&w=2
>
> Thanks,
> Giridhar.M.B
>
>
>
> On Sep 24, 2009, at 7:42 AM, Michael Reed wrote:
>
>> Hello,
>>
>> The purpose of the queue full tracking patch in qla2xxx is to
>> keep the driver from changing a user space override of the queue
>> depth back to what the driver believes is the "correct" value.
>>
>> The raid devices that we use have per raid controller queue depth
>> limits and have at times demonstrated, uh, bad behavior when
>> their queues are full for sustained periods of time. SGI needs
>> to be able to set queue depth for a lun based upon access patterns
>> and performance requirements of the entire cluster and know that
>> it will be honored as an upper bound.
>>
>> Might you provide a pointer to the recently submitted patches?
>> I haven't followed linux-scsi in a while.... I'll be quite
>> happy to take a look.
>>
>> Thanks,
>> Mike
>>
>>
>> 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.
>>>
>>>
>>> Thanks,
>>> Giridhar.M.B
>>>
>>> --
>>> 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
>
next prev parent reply other threads:[~2009-09-24 19:15 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 [this message]
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
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=4ABBC53F.9090203@sgi.com \
--to=mdr@sgi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andrew.vasquez@qlogic.com \
--cc=giridhar.malavali@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--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).