Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Jens Axboe <axboe@suse.de>,
	Andrew Vasquez <andrew.vasquez@qlogic.com>,
	Linux-SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: calling scsi_adjust_queue_depth() during I/O...
Date: Fri, 05 Aug 2005 11:32:07 -0500	[thread overview]
Message-ID: <1123259528.5003.36.camel@mulgrave> (raw)
In-Reply-To: <20050805123301.GA3311@htj.dyndns.org>

On Fri, 2005-08-05 at 21:33 +0900, Tejun Heo wrote:
>  Here's the fix.  It basically revives bqt->real_max_depth sans
> allocation optimization in init_tag_map.  I've also added a comment
> explicitly noting that tag map cannot be shrunk to prevent other
> morons like me.  :-( Please try this one and let me know how it works.
> If this is the correct fix, I'll repost properly to Jens and lkml with
> detailed explanation on how it was broken in the original code and how
> I broke it with my previous patch.  Sorry.

Actually, if you really want to adjust the array size downwards, there's
a way we can do it:

- If the bits that would be lost on shrinkage are all zero at the time
blk_queue_resize_tags() is called, that means that there are no
outstanding tags up there and the array can be shrunk immediately.

- If there are outstanding tags between the new and the old depth, the
array can be shrunk when the last one of these returns, say in
blk_rq_end_tag()

James



  parent reply	other threads:[~2005-08-05 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-04 23:41 calling scsi_adjust_queue_depth() during I/O Andrew Vasquez
2005-08-05  7:57 ` Jens Axboe
2005-08-05 11:09   ` Tejun Heo
2005-08-05 11:43     ` Tejun Heo
2005-08-05 12:33       ` Tejun Heo
2005-08-05 15:55         ` Andrew Vasquez
2005-08-05 15:59           ` Jens Axboe
2005-08-05 17:15             ` Tejun Heo
2005-08-05 16:32         ` James Bottomley [this message]
2005-08-05 17:10           ` Tejun Heo
2005-08-05 17:20             ` James Bottomley
2005-08-05 17:24             ` 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=1123259528.5003.36.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=andrew.vasquez@qlogic.com \
    --cc=axboe@suse.de \
    --cc=htejun@gmail.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