public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2.5.17] Making SCSI not copy the request structure
Date: Wed, 22 May 2002 18:53:49 -0400	[thread overview]
Message-ID: <20020522185349.D2819@redhat.com> (raw)
In-Reply-To: <20020522154406.A17222@eng2.beaverton.ibm.com>; from patmans@us.ibm.com on Wed, May 22, 2002 at 03:44:06PM -0700

On Wed, May 22, 2002 at 03:44:06PM -0700, Patrick Mansfield wrote:
> Do you think the queue depth on some of the adapters/devices should be
> shrunk or the request queue increased with your patch? Some adapters set

Actually, more appropriate for future versions would be to make the queue
depth adjustable.  Justin's aic driver sets the depth to 253 because he
can't increase it later if he wants to, but he can queue things up
internally if he ever needs to decrease it.  If low level drivers had some
way of signalling up the stack "hey, this is how many queue slots I can
handle on this particular device now" at their leisure, then that would be
a far superior option to what we have now which is the mid layer saying to
the low level drivers "OK, tell me how many commands you can support on
this list of devices and you have to stick with that until the next
reboot".  So, instead of the mid layer calling into the low level driver 
to tell it to set queue depths, I think the low level driver should be 
allowed to call into the mid layer and have the mid layer adjust the queue 
depth on a device.  This should, of course, be properly locked so that a 
low level driver can change it's mind about a device's queue depth later 
if it wishes and call back into the mid layer with a new queue depth 
value without confusing the mid layer.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  reply	other threads:[~2002-05-22 22:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 23:11 [PATCH 2.5.17] Making SCSI not copy the request structure James Bottomley
2002-05-22 22:44 ` Patrick Mansfield
2002-05-22 22:53   ` Doug Ledford [this message]
2002-05-23  2:01     ` Alan Cox
2002-05-23  3:14       ` Doug Ledford
2002-05-24 15:32         ` Alan Cox
2002-05-24 15:56           ` James Bottomley
2002-05-23  0:06   ` James Bottomley
  -- strict thread matches above, loose matches on Subject: below --
2002-05-23  9:18 Aron Zeh
2002-05-23 12:44 ` James Bottomley
2002-05-24  7:52 Aron Zeh
2002-05-24  8:34 ` rakesh rakesh
2002-05-24 13:17   ` James Bottomley
2002-05-24 13:00 ` James Bottomley
2002-05-24  9:35 Aron Zeh
2002-05-24 16:44 ` Patrick Mansfield
2002-05-31 12:04 Aron Zeh
     [not found] <OFF6A89763.CD0EBEF7-ONC1256BCA.003CD69A@de.ibm.com>
2002-05-31 13:57 ` James Bottomley
2002-05-31 16:57 Aron Zeh

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=20020522185349.D2819@redhat.com \
    --to=dledford@redhat.com \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=patmans@us.ibm.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