From: Jeff Garzik <jgarzik@pobox.com>
To: kallol@nucleodyne.com
Cc: Mark Lord <liml@rtr.ca>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Fwd: Re: Performance figure for sx8 driver
Date: Sun, 12 Jun 2005 23:39:25 -0400 [thread overview]
Message-ID: <42ACFFED.9050701@pobox.com> (raw)
In-Reply-To: <1118598197.25250.20.camel@driver>
Kallol Biswas wrote:
> I have been investigating what the cause of performance loss could be.
>
> I have noticed several things:
>
> 0) Setting to CARM_MAX_Q to 30 hangs. So we have been testing only with
> CARM_MAX_Q == 1. The firmware has not been updated yet.
Note that CARM_MAX_Q controls the --host-- queue.
This means that, with CARM_MAX_Q==1, only one command can be sent to
--any-- disk, at a time. disks 1-7 must wait for disk 0 to complete an
I/O, and so on. Each command is host-synchronous.
As such, this limits multi-disk performance quite severely, but does not
hamper single disk performance.
CARM_MAX_Q==1 is set as such (as mentioned earlier in the thread)
because early firmwares would lock up if that value was increased.
It has been reported that newer firmwares work fine with CARM_MAX_Q==30,
which completely eliminates the host-synchronous condition.
Jeff
next prev parent reply other threads:[~2005-06-13 3:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 6:18 Fwd: Re: Performance figure for sx8 driver kallol
2005-06-12 16:30 ` Mark Lord
2005-06-12 17:43 ` Kallol Biswas
2005-06-13 3:39 ` Jeff Garzik [this message]
2005-06-27 1:11 ` Enabling MSI on SATAII150 Kallol Biswas
2005-06-27 3:54 ` Jeff Garzik
2005-08-20 6:19 ` Jeff Garzik
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=42ACFFED.9050701@pobox.com \
--to=jgarzik@pobox.com \
--cc=kallol@nucleodyne.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).