From: Jens Axboe <jens.axboe@oracle.com>
To: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 3/8] cciss: change number of commands per controller
Date: Thu, 2 Nov 2006 15:39:45 +0100 [thread overview]
Message-ID: <20061102143945.GM13555@kernel.dk> (raw)
In-Reply-To: <20061102143318.GB16430@beardog.cca.cpqcorp.net>
On Thu, Nov 02 2006, Mike Miller (OS Dev) wrote:
> On Thu, Nov 02, 2006 at 03:11:50PM +0100, Jens Axboe wrote:
> > On Wed, Nov 01 2006, Mike Miller (OS Dev) wrote:
> > > + {0x3211103C, "Smart Array E200i", &SA5_access, 120},
> >
> > Is it 120, or 128? And how big is the allocated command array now, with
> > 512 commands?
>
> The controller can handle up to 128, but I artificially limited it to 120
> for reasons I shouldn't discuss in public. :)
:-)
> Each command is 548 bytes w/o scatter gather chaining. So 548 * 512 = 280576
> bytes for the command list. We've tested using 1024 commands with several
> Smart Array controllers and have not encountered issues. The reason for the
> increase is performance. The busier you can keep the controller the better
> it works.
So this:
hba[i]->cmd_pool = (CommandList_struct *)
pci_alloc_consistent(hba[i]->pdev,
NR_CMDS * sizeof(CommandList_struct),
&(hba[i]->cmd_pool_dhandle));
is getting pretty huge then (it was already, actually).
--
Jens Axboe
prev parent reply other threads:[~2006-11-02 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 21:56 [PATCH 3/8] cciss: change number of commands per controller Mike Miller (OS Dev)
2006-11-02 14:11 ` Jens Axboe
2006-11-02 14:33 ` Mike Miller (OS Dev)
2006-11-02 14:39 ` Jens Axboe [this message]
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=20061102143945.GM13555@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikem@beardog.cca.cpqcorp.net \
/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