public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernard Blackham <bernard@blackham.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Matthew Collins <matt@signalz.com>, linux-kernel@vger.kernel.org
Subject: Re: Promise SX8 performance issues and CARM_MAX_Q
Date: Fri, 25 Mar 2005 12:47:04 +0800	[thread overview]
Message-ID: <20050325044704.GF4300@blackham.com.au> (raw)
In-Reply-To: <42438EED.4020202@pobox.com>

On Thu, Mar 24, 2005 at 11:09:17PM -0500, Jeff Garzik wrote:
> >Indeed there does seem to be new firmware out as of 2/23/05. I ran my 
> >tests with the 9/10/04 firmware but I did not adjust the CARM_MAX_Q 
> >value. Do either of you happen to know what firmware revisions you 
> >tested under?

BIOS boot messages didn't seem to indicate a firmware version, but
this card was only available in stock in early March, so its fairly
likely to have the latest firmware (2/23/05).

> The driver should be solid for _at least_ CARM_MAX_Q==31, presuming that 
> the firmware doesn't choke.

We've run it here with CARM_MAX_Q = 32 with a custom stress testing
script and haven't had any incidents so far. CARM_MAX_Q = 33 goes
bad instantly.

> (c) stress the card with fsx, badblocks, iozone, and other tools
>     on -multiple ports- simultaneously.

I'll give those a workout over the weekend and let you know the
results.

Thanks,

Bernard.

-- 
 Bernard Blackham <bernard at blackham dot com dot au>

  reply	other threads:[~2005-03-25  4:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-29 19:50 Promise SX8 driver performance Matt
2005-03-23 17:57 ` Promise SX8 performance issues and CARM_MAX_Q Bernard Blackham
2005-03-23 23:16   ` Jeff Garzik
2005-03-23 23:25     ` Matthew Collins
2005-03-25  4:09       ` Jeff Garzik
2005-03-25  4:47         ` Bernard Blackham [this message]
2005-03-26 14:12         ` Bernard Blackham

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=20050325044704.GF4300@blackham.com.au \
    --to=bernard@blackham.com.au \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt@signalz.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