From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi : set target can_queue from devinfo flags
Date: Wed, 14 May 2008 15:38:13 -0400 [thread overview]
Message-ID: <1210793893.3075.6.camel@localhost.localdomain> (raw)
In-Reply-To: <1210700704.16304.1.camel@localhost.localdomain>
On Tue, 2008-05-13 at 13:45 -0400, James Smart wrote:
> This patch, discussed in the initial thread on target can_queue limits
> (see http://marc.info/?l=linux-scsi&m=120944296225094&w=2 )
> allows the target can_queue limit to be obtained from the device list based on
> Inquiry data obtained during scan.
>
> I have pinged several of the array vendors to supply target-port level values
> for their arrays. Hopefully, we will see them populate the device list with some
> real values shortly.
>
> This patch was cut against scsi-misc-2.6, and depends on Mike Christies patches
> contained in the original thread.
Just from a point of first principles, what makes you think the target
port queue depth of an array is anything like constant? All the
information I've got back from array vendors over the years leads me to
conclude that it's dynamically determined based on resources available
at the time the array services the request. Additionally, I've been
told that even a heuristic rule of thumb value varies with the array
cache size (which is a quantity not reflected in the inquiry strings).
My best guess for the way of handling this is that we should be using
the Doug Leaford track_queue_full infrastructure but on a per target
bases.
James
next prev parent reply other threads:[~2008-05-14 21:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-13 17:45 [PATCH] scsi : set target can_queue from devinfo flags James Smart
2008-05-14 6:34 ` Hannes Reinecke
2008-05-14 14:39 ` James Smart
2008-05-14 15:01 ` Hannes Reinecke
2008-05-14 19:38 ` James Bottomley [this message]
2008-05-14 21:50 ` James Smart
2008-05-15 1:21 ` James Smart
2008-09-24 19:13 ` Mike Christie
2008-09-24 19:17 ` Mike Christie
2008-09-25 18:40 ` Mike Christie
2008-09-25 19:03 ` James Smart
2008-09-24 19:38 ` James Smart
2008-09-25 18:15 ` Mike Christie
2008-09-26 7:46 ` Hannes Reinecke
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=1210793893.3075.6.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=James.Smart@Emulex.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