From: Jeremy Higdon <jeremy@sgi.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [RFC PATCH 2.6.9-rc2] Add sysfs queue depth override to qla2xxx
Date: Tue, 28 Sep 2004 17:36:11 -0700 [thread overview]
Message-ID: <20040929003611.GK192475@sgi.com> (raw)
In-Reply-To: <1096401196.2008.97.camel@mulgrave>
So do we have a consensus on what the driver should limit queue
depth to? Currently, it's 32 or ql2xmaxqdepth, if that was specified.
>From what I can see, ql2xmaxqdepth is effectively limited to 65535.
We don't want one lun to use host driver or host adapter resources
to the point that it starves other luns. Ideally, the max would
depend on what else was attached, but I don't think we want to
make this too complicated. Anyone changing the queue depth should
have a clue about what they're doing.
Andrew, how many command slots are there in the various adapters,
and do the continuation entries each eat a command slot?
jeremy
next prev parent reply other threads:[~2004-09-29 0:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 16:52 [RFC PATCH 2.6.9-rc2] Add sysfs queue depth override to qla2xxx 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 [this message]
2004-09-29 16:41 ` Andrew Vasquez
2004-09-29 22:12 ` Jeremy Higdon
-- strict thread matches above, loose matches on Subject: below --
2004-09-28 16:54 Andrew Vasquez
2004-09-27 6:10 Jeremy Higdon
2004-09-27 6:25 ` Jeremy Higdon
2004-09-28 7:54 ` Jeremy Higdon
2004-09-28 14:05 ` James Bottomley
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=20040929003611.GK192475@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).