linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Higdon <jeremy@sgi.com>
To: linux-scsi@vger.kernel.org
Cc: andrew.vasquez@qlogic.com, James.Bottomley@steeleye.com
Subject: Re: [RFC PATCH 2.6.9-rc2] Add sysfs queue depth override to qla2xxx
Date: Tue, 28 Sep 2004 00:54:07 -0700	[thread overview]
Message-ID: <20040928075407.GA190115@sgi.com> (raw)
In-Reply-To: <20040927061003.GA182890@sgi.com>

On Sun, Sep 26, 2004 at 11:10:03PM -0700, Jeremy Higdon wrote:
> This patch is to QLA2xxx version 8.00.00b15-k, and it allows users
> to override the default driver queue depth for a target by making
> the queue_depth sysfs attribute writeable.
> 
> I based this on the code in the 53c700 driver.
> 
> Andrew, please apply if it looks correct to you and James.
> 
> Let me know if you'd like me to regenerate against a different qla2xxx
> version.
> 
> thanks
> 
> Jeremy

Found a bug in the patch.  It returned an incorrect count if tagged_supported
was not true.

signed-off-by: Jeremy Higdon  <jeremy@sgi.com>


===== drivers/scsi/qla2xxx/qla_os.c 1.41 vs edited =====
--- 1.41/drivers/scsi/qla2xxx/qla_os.c	2004-08-09 16:48:29 -07:00
+++ edited/drivers/scsi/qla2xxx/qla_os.c	2004-09-28 00:34:50 -07:00
@@ -159,6 +159,20 @@
 
 static int qla2x00_proc_info(struct Scsi_Host *, char *, char **,
     off_t, int, int);
+static ssize_t qla2xxx_store_queue_depth(struct device *dev, const char *buf, size_t count);
+
+static struct device_attribute qla2xxx_queue_depth_attr = {
+	.attr = {
+		.name =		"queue_depth",
+		.mode =		S_IWUSR,
+	},
+	.store = qla2xxx_store_queue_depth,
+};
+
+static struct device_attribute *qla2xxx_dev_attrs[] = {
+	&qla2xxx_queue_depth_attr,
+	NULL,
+};
 
 static struct scsi_host_template qla2x00_driver_template = {
 	.module			= THIS_MODULE,
@@ -184,6 +198,8 @@
 	 * which equates to 0x800000 sectors.
 	 */
 	.max_sectors		= 0xFFFF,
+
+	.sdev_attrs		= qla2xxx_dev_attrs,
 };
 
 static struct scsi_transport_template *qla2xxx_transport_template = NULL;
@@ -1797,6 +1813,21 @@
 	}
 
 	return (0);
+}
+
+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;
+		scsi_adjust_queue_depth(sdev, MSG_ORDERED_TAG, depth);
+	}
+	return count;
 }
 
 /**

  parent reply	other threads:[~2004-09-28  7:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-27  6:10 [RFC PATCH 2.6.9-rc2] Add sysfs queue depth override to qla2xxx Jeremy Higdon
2004-09-27  6:25 ` Jeremy Higdon
2004-09-28  7:54 ` Jeremy Higdon [this message]
2004-09-28 14:05   ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2004-09-28 16:52 Andrew Vasquez
2004-09-28 19:36 ` Jeremy Higdon
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
2004-09-28 16:54 Andrew Vasquez

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=20040928075407.GA190115@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).