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 12:20:31 -0500 [thread overview]
Message-ID: <1123262432.5003.44.camel@mulgrave> (raw)
In-Reply-To: <20050805171034.GA5046@htj.dyndns.org>
On Sat, 2005-08-06 at 02:10 +0900, Tejun Heo wrote:
> Yes, we can do that, but I'm not sure if that would be necessary.
> AFAIK, queues are normally not very deep and a tag only occupies one
> pointer and one bit. Also, the shrinking operation isn't very common,
> at least for traditional SPI devices and SATA drives, I think.
>
> Are newer SCSI devices (say, SAS/iSCSI) different? - like having very
> deep queue and needing dynamic queue depth adjustment? If that's the
> case, I think I can implement shrinking in a separate patch. (and try
> not to screw up this time ;-)
Well, yes, there are reasons for wanting deeper queues, but I'd leave it
for the time being.
What I'm looking into is support for aic7xxx/aic79xx queueing. There,
the sequencer has to have a globally unique tag (from which it generates
the device locally unique tag internally). That gives TCQ depths of up
to 512 I believe. However, still probably not a significant waste of
memory to worry about.
James
next prev parent reply other threads:[~2005-08-05 17:20 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
2005-08-05 17:10 ` Tejun Heo
2005-08-05 17:20 ` James Bottomley [this message]
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=1123262432.5003.44.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