All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Vasu Dev <vasu.dev@intel.com>
Cc: michaelc@cs.wisc.edu, linux-scsi@vger.kernel.org
Subject: Re: [RFC PATCH 3/9] drivers: convert drivers setting the	change_queue_depth callback
Date: Wed, 26 Aug 2009 14:19:47 -0400	[thread overview]
Message-ID: <4A957CC3.6080605@garzik.org> (raw)
In-Reply-To: <20090826180331.23396.77062.stgit@vi1.jf.intel.com>

On 08/26/2009 02:03 PM, Vasu Dev wrote:
> From: Mike Christie<michaelc@cs.wisc.edu>
>
> This is a simple port of the drivers setting a change_queue_depth
> callback but were not tracking queue fulls. In the patch I just have
> these LLDs adjust the queue depth if the user was requesting it.

Where is the doc describing how, and why, queue-full tracking occurs?


> diff --git a/drivers/ata/sata_nv.c b/drivers/ata/sata_nv.c
> index 86a4058..fb28be9 100644
> --- a/drivers/ata/sata_nv.c
> +++ b/drivers/ata/sata_nv.c
> @@ -1963,7 +1963,7 @@ static int nv_swncq_slave_config(struct scsi_device *sdev)
>   	ata_id_c_string(dev->id, model_num, ATA_ID_PROD, sizeof(model_num));
>
>   	if (strncmp(model_num, "Maxtor", 6) == 0) {
> -		ata_scsi_change_queue_depth(sdev, 1);
> +		ata_scsi_change_queue_depth(sdev, 1, SCSI_QDEPTH_SYSFS_REQ);
>   		ata_dev_printk(dev, KERN_NOTICE,
>   			"Disabling SWNCQ mode (depth %x)\n", sdev->queue_depth);
>   	}

This queue depth change was clearly not requested via sysfs...

	Jeff




  reply	other threads:[~2009-08-26 18:19 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
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 [this message]
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=4A957CC3.6080605@garzik.org \
    --to=jeff@garzik.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.