From: Douglas Gilbert <dougg@torque.net>
To: Tameen Khan <tameen@andiamo.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: setting maximum queue depth to 255 with sg driver
Date: Fri, 30 May 2003 19:24:41 +1000 [thread overview]
Message-ID: <3ED72359.9020202@torque.net> (raw)
In-Reply-To: <4.3.2.7.2.20030529235329.029e0740@andiamo.com>
Tameen Khan wrote:
> goal is to achieve a max queue depth of 255 using qlogic hba qla2342 on
> a linux host (2.4.18)
> I am using scsi generic driver to do IO. The queue depth bottleneck is
> SG_MAX_QUEUE as indicated in the documentation.
> The SG_MAX_QUEUE value is 16
> I've tried one way to bypass this limit (as suggested in
> http://tldp.org/HOWTO/SCSI-Generic-HOWTO/)
> That is to do multiple open() to the same device, SG driver should allow
> queueing of 16
> commands per device.
... commands per open file descriptor.
> This does not work for me and I still see a maximum queue depth of 16.
Tameen,
In what sense doesn't it work; something wrong with the
sg driver or doesn't fit your code?
> What could be the reason and what could be a workaround ?
> What could be other ways to increase the queue depth beyond 16 ?
You can of course change SG_MAX_QUEUE to 255 and recompile
the sg driver. At the time that code was written (early lk 2.2
series) there was often a shortage of RAM so the idea was
to predefine resources at open() and if that succeeded reasonable
guarantees could be given that subsequent operations would not
fail with ENOMEM. This was (and still is) important to applications
like cdrecord and its predecessor cdwrite.
Doug Gilbert
next prev parent reply other threads:[~2003-05-30 9:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 7:06 setting maximum queue depth to 255 with sg driver Tameen Khan
2003-05-30 9:24 ` Douglas Gilbert [this message]
2003-05-30 16:41 ` Tameen Khan
-- strict thread matches above, loose matches on Subject: below --
2003-05-30 17:38 Duane Grigsby
[not found] <41EBA11203419D4CA8EB4C6140D8B40101021138@AVEXCH01.qlogic.o rg>
2003-05-30 18:43 ` Tameen Khan
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=3ED72359.9020202@torque.net \
--to=dougg@torque.net \
--cc=linux-scsi@vger.kernel.org \
--cc=tameen@andiamo.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