linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Warner <andyw@pobox.com>
To: Marc Bevand <bevand_m@epita.fr>
Cc: linux-ide@vger.kernel.org
Subject: Re: libata problems with 66Mhz Promise SATA150 TX4
Date: Tue, 14 Sep 2004 19:18:51 -0500	[thread overview]
Message-ID: <20040914191851.A7263@florence.linkmargin.com> (raw)
In-Reply-To: <41473287.7050101@epita.fr>; from bevand_m@epita.fr on Tue, Sep 14, 2004 at 08:03:51PM +0200

Marc Bevand wrote:
> [...]
> An easy way to reproduce the problem is to run 4 instances of 'dd' reading
> from 4 disks at the same time. It is much harder to reproduce when reading
> from 3 disks, and quasi-impossible to reproduce when reading from 2 disks.

I've tried, but cannot reproduce it here.

System is:
 - Dual Xeon Dell Poweredge 2600
 - Promise TX4 in 100MHz PCI-X slot.
 - 4 x Seagate ST3160023AS
 - 2.6.9-rc1

I've tried both dd and sg_utils, can't make it fail - no way, no how.

> [...]
> It seems the Promise chip has some problems under high-load conditions:
> the throughput I obtain when reading from 4 disks is 100 MB/s (at 33MHz)
> and 215 MB/s (at 66MHz)...

I'm observing a lower throughput than that, though ~60MB/s; so I'm
going to check to see if there is something else throttling
performance, below the point of failure.
-- 
andyw@pobox.com

Andy Warner		Voice: (612) 801-8549	Fax: (208) 575-5634

  parent reply	other threads:[~2004-09-15  0:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-13 21:14 libata problems with 66Mhz Promise SATA150 TX4 Paul Fisher
2004-09-14 18:03 ` Marc Bevand
2004-09-14 23:13   ` Jeff Garzik
2004-09-15  0:18   ` Andy Warner [this message]
2004-09-15  9:02     ` Marc Bevand
2004-09-15 13:08       ` Andy Warner
2004-09-15 13:45         ` Marc Bevand
2004-10-04  9:10           ` Generic bug/race in the IDE/SATA code ? Marc Bevand

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=20040914191851.A7263@florence.linkmargin.com \
    --to=andyw@pobox.com \
    --cc=bevand_m@epita.fr \
    --cc=linux-ide@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).