From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Miller <mike.miller@hp.com>
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/1] cciss: read config to obtain max outstanding commands per controller
Date: Tue, 1 Jul 2008 14:23:08 -0700 [thread overview]
Message-ID: <20080701142308.4958bc5f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080701210247.GA5095@roadking.ldev.net>
On Tue, 1 Jul 2008 16:02:47 -0500
Mike Miller <mike.miller@hp.com> wrote:
> This patch changes the way we determine the maximum number of outstanding
> commands for each controller. Most Smart Array controllers can support up
> to 1024 commands, the notable exceptions are the E200 and E200i.
> The next generation of controllers which were just added support a mode of
> operation called Zero Memory Raid (ZMR). In this mode they only support 64
> outstanding commands. In Full Function Raid (FFR) mode they support 1024.
> We have been setting the queue depth by arbitrarily assigning some value for
> each controller. We needed a better way to set the queue depth to avoid lots
> of annoying "fifo full" messages. So we made the driver a little smarter. We
> now read the config table and subtract 4 from the returned value. The -4 is
> to allow some room for ioctl calls which are not tracked the same way as io
> commands are tracked.
What would be the effect of _not_ having this patch upon users of the
new hardware?
If the answer is "bad" then we should get this change into 2.6.26 and
2.6.25.x, because people will surely be running those kernels on the
new hardware.
next prev parent reply other threads:[~2008-07-01 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 21:02 Mike Miller
2008-07-01 21:23 ` Andrew Morton [this message]
2008-07-07 15:12 ` Miller, Mike (OS Dev)
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=20080701142308.4958bc5f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mike.miller@hp.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
Powered by JetHome