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: Sat, 26 Mar 2005 22:12:11 +0800	[thread overview]
Message-ID: <20050326141210.GJ4300@blackham.com.au> (raw)
In-Reply-To: <42438EED.4020202@pobox.com>

On Thu, Mar 24, 2005 at 11:09:17PM -0500, Jeff Garzik wrote:
> The driver was developed on a pre-production board, so its entirely 
> possible Promise fixed this issue.
> 
> The driver should be solid for _at least_ CARM_MAX_Q==31, presuming that 
> the firmware doesn't choke.

Stressing this SX8 card broke with CARM_MAX_Q anything higher than
16. Tests included simultaneous iozones, bonnie++'s, fsx, badblocks,
and mkfs'ing, on 4 ports. Setting CARM_MAX_Q to 17 or above
resulted in errors such as:

Buffer I/O error on device sx80_0p1, logical block 108828
lost page write due to I/O error on sx80_0p1
end_request: I/O error, dev sx80_2, sector 389167

It's been thrashing away with various tests most of today with
CARM_MAX_Q = 16, and it hasn't missed a beat.

Thanks must go to Matt Johnston who actually did all the work of
giving the card and drives a hard time.

Bernard.

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

      parent reply	other threads:[~2005-03-26 14:12 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
2005-03-26 14:12         ` Bernard Blackham [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=20050326141210.GJ4300@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