From: Christof Schmitt <christof.schmitt@de.ibm.com>
To: Vasu Dev <vasu.dev@intel.com>
Cc: michaelc@cs.wisc.edu, linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH 1/9] scsi-ml: modify change_queue_depth to take in reason why it is being called
Date: Thu, 27 Aug 2009 12:21:36 +0200 [thread overview]
Message-ID: <20090827102135.GB5125@schmichrtp> (raw)
In-Reply-To: <20090826180320.23396.70657.stgit@vi1.jf.intel.com>
On Wed, Aug 26, 2009 at 11:03:20AM -0700, Vasu Dev wrote:
> --- a/include/scsi/scsi_host.h
> +++ b/include/scsi/scsi_host.h
> @@ -43,6 +43,13 @@ struct blk_queue_tags;
> #define DISABLE_CLUSTERING 0
> #define ENABLE_CLUSTERING 1
>
> +enum {
> + SCSI_QDEPTH_SYSFS_REQ, /* user requested change through sysfs */
> + SCSI_QDEPTH_QFULL, /* scsi-ml requested due to queue full */
> + SCSI_QDEPTH_RAMP_UP, /* scsi-ml requested due to threshhold event */
> + SCSI_QDEPTH_RAMP_DOWN, /* LLD/class requested due to lld/class event */
> +};
> +
> struct scsi_host_template {
> struct module *module;
> const char *name;
I did not find SCSI_QDEPTH_RAMP_DOWN being used. Would a LLD use this
internally when changing the queue depth?
--
Christof Schmitt
next prev parent reply other threads:[~2009-08-27 10:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 18:03 [RFC PATCH 0/9] RFC: handle queue_depth adjustments because of QUEUE_FULLs in scsi_error.c Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 1/9] scsi-ml: modify change_queue_depth to take in reason why it is being called Vasu Dev
2009-08-27 10:21 ` Christof Schmitt [this message]
2009-08-27 21:09 ` Vasu Dev
2009-08-28 16:56 ` Mike Christie
2009-08-26 18:03 ` [RFC PATCH 2/9] scsi error: have scsi-ml call change_queue_depth to handle QUEUE_FULL Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 3/9] drivers: convert drivers setting the change_queue_depth callback Vasu Dev
2009-08-26 18:19 ` Jeff Garzik
2009-08-26 21:50 ` Vasu Dev
2009-08-26 21:55 ` Mike Christie
2009-08-26 18:03 ` [RFC PATCH 4/9] drivers: convert fc drivers calling scsi_track_queue_full Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 5/9] scsi: updates sdev to add queue_depth ramp up code Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 6/9] scsi: adds sdev->queue_ramp_up_period to sysfs Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 7/9] scsi: add common queue_depth ramp up code Vasu Dev
2009-08-26 18:03 ` [RFC PATCH 8/9] fcoe, libfc: fix an libfc issue with queue ramp down in libfc Vasu Dev
2009-08-26 18:04 ` [RFC PATCH 9/9] libfc: adds queue_depth ramp up to libfc Vasu Dev
2009-08-27 10:19 ` Christof Schmitt
2009-08-27 20:56 ` Vasu Dev
2009-08-28 10:44 ` Christof Schmitt
2009-09-02 18:00 ` Vasu Dev
2009-09-01 22:57 ` [RFC PATCH 0/9] RFC: handle queue_depth adjustments because of QUEUE_FULLs in scsi_error.c Vasu Dev
2009-09-02 1:46 ` Mike Christie
2009-09-02 18:01 ` Vasu Dev
2009-09-03 8:17 ` Swen Schillig
2009-09-14 11:21 ` Christof Schmitt
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=20090827102135.GB5125@schmichrtp \
--to=christof.schmitt@de.ibm.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