linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@sgi.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: linux-scsi@vger.kernel.org, James.Bottomley@steeleye.com
Subject: Re: [RFC PATCH 2.6.9-rc2] Add sysfs queue depth override to qla2xxx
Date: Tue, 28 Sep 2004 12:36:14 -0700	[thread overview]
Message-ID: <20040928193614.GB192475@sgi.com> (raw)
In-Reply-To: <B179AE41C1147041AA1121F44614F0B0012AD92B@AVEXCH02.qlogic.org>

On Tue, Sep 28, 2004 at 09:52:55AM -0700, Andrew Vasquez wrote:
> On Tuesday, September 28, 2004 12:54 AM, Jeremy Higdon wrote:
> > +static ssize_t
> > +qla2xxx_store_queue_depth(struct device *dev, const char *buf,
> > size_t count) +{
> > +	int			 depth;
> > +	struct scsi_device	*sdev = to_scsi_device(dev);
> > +
> > +	if (sdev->tagged_supported) {
> > +		depth = simple_strtoul(buf, NULL, 0);
> > +		if (depth > ql2xmaxqdepth)
> > +			depth = ql2xmaxqdepth;
> 
> Any particular reason why the ql2xmaxqdepth module-parameter is
> being used as a high-water limit?  The module-param is (was) used 
> as a global setting of queue-depth for all luns (quite inflexible).
> By overriding:
> 
> 	/sys/class/scsi_device/22:0:0:0/device/queue_depth
> 
> with a writable value, a user should be allowed to update the
> value to something higher (max(unsigned short)?) based on the 
> back-end storage.


I was trying to be conservative -- I didn't know the reason for
that limit.  By all means, let's remove it then.

Would you like me to regenerate the patch, or do you just want
to apply it to your internal source that will eventually be
fed back to us?

jeremy

  reply	other threads:[~2004-09-28 19:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 16:52 [RFC PATCH 2.6.9-rc2] Add sysfs queue depth override to qla2xxx Andrew Vasquez
2004-09-28 19:36 ` Jeremy Higdon [this message]
2004-09-28 19:53   ` James Bottomley
2004-09-28 20:12     ` Jens Axboe
2004-09-28 20:34       ` Andrew Vasquez
2004-09-29  6:21         ` Jens Axboe
2004-09-29  6:57           ` Jeremy Higdon
2004-09-29  6:56             ` Jens Axboe
2004-09-29  0:36     ` Jeremy Higdon
2004-09-29 16:41       ` Andrew Vasquez
2004-09-29 22:12         ` Jeremy Higdon
  -- strict thread matches above, loose matches on Subject: below --
2004-09-28 16:54 Andrew Vasquez
2004-09-27  6:10 Jeremy Higdon
2004-09-27  6:25 ` Jeremy Higdon
2004-09-28  7:54 ` Jeremy Higdon
2004-09-28 14:05   ` 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=20040928193614.GB192475@sgi.com \
    --to=jeremy@sgi.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=linux-scsi@vger.kernel.org \
    /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).