mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Anderson <andmike@us.ibm.com>
To: Andrew Morton <akpm@digeo.com>
Cc: Patrick Mansfield <patmans@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.62-mm2 slow file system writes across multiple disks
Date: Wed, 26 Feb 2003 09:18:57 -0800	[thread overview]
Message-ID: <20030226171857.GA1134@beaverton.ibm.com> (raw)
In-Reply-To: <20030226004454.2bfd8deb.akpm@digeo.com>

Andrew Morton [akpm@digeo.com] wrote:
> 
> > It would be nice if a larger queue depth did not kill performance.
> 
> Does the other qlogic driver exhibit the same thing?

Well the qlogic provided driver should exhibit slightly different
behavior as its per device queue depth is 16 and the request ring count
is 128.

The feral driver is currently running a per device queue of 63 and a
request ring size of 64. (if I am reading the driver correctly?). When
the request count is exceeded I believe it should return a 1 to the call
of queuecommand. Can you tell if scsi_queue_insert is being called.

> > The larger queue depths can be nice for disk arrays with lots of cache and
> > (more) random IO patterns.
> 
> So says the scsi lore ;)  Have you observed this yourself?  Have you
> any numbers handy?

I do not have current numbers but you need to get the command on the
wire to get any benefit.

-andmike
--
Michael Anderson
andmike@us.ibm.com


  parent reply	other threads:[~2003-02-26 17:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 20:03 Patrick Mansfield
2003-02-24 21:53 ` Andrew Morton
2003-02-25  1:47   ` Patrick Mansfield
2003-02-25  4:43     ` Andrew Morton
2003-02-25 19:24       ` Patrick Mansfield
2003-02-26  8:44         ` Andrew Morton
2003-02-26 12:17           ` Helge Hafting
2003-02-26 17:18           ` Mike Anderson [this message]
2003-02-28  1:57           ` Patrick Mansfield

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=20030226171857.GA1134@beaverton.ibm.com \
    --to=andmike@us.ibm.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®