linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Paul Jakma <paul@clubi.ie>
Cc: linux-ide@vger.kernel.org, Ricky Beam <jfbeam@bluetronic.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix sata_sil quirk
Date: Tue, 22 Jun 2004 23:39:54 -0400	[thread overview]
Message-ID: <40D8FB8A.8040109@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0406230421220.2702@fogarty.jakma.org>

Paul Jakma wrote:
> # cat /proc/scsi/scsi
> Attached devices:
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: WDC WD1600JD-00G Rev: 02.0
>   Type:   Direct-Access                    ANSI SCSI revision: 05
> Host: scsi1 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: WDC WD1600JD-00G Rev: 02.0
>   Type:   Direct-Access                    ANSI SCSI revision: 05
> Host: scsi2 Channel: 00 Id: 00 Lun: 00
>   Vendor: ATA      Model: WDC WD1600JD-00G Rev: 02.0
>   Type:   Direct-Access                    ANSI SCSI revision: 05

> And am not having (touch wood) any stability problems using these disks 
> with linux md RAID1 and RAID5. Though, they're in a K6-II 350, so 
> performance is slow anyway. (i get about 25MB/s absolute max reading 
> from a RAID-5 array).


Cool.  Yeah, non-Seagate should be full speed and unaffected...

	Jeff



  reply	other threads:[~2004-06-23  3:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-22 20:22 [PATCH] fix sata_sil quirk Jeff Garzik
2004-06-22 20:29 ` Ricky Beam
2004-06-22 20:41   ` Jeff Garzik
2004-06-22 22:12   ` Jeff Garzik
2004-06-23  0:34     ` Ricky Beam
2004-06-23  3:24 ` Paul Jakma
2004-06-23  3:39   ` Jeff Garzik [this message]
2004-06-23  3:46     ` Paul Jakma
2004-06-23  3:51       ` Jeff Garzik
2004-06-23  6:34         ` Ricky Beam
     [not found]           ` <20040628015431.GA31687@trot.local>
2004-09-27  3:40             ` George Georgalis

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=40D8FB8A.8040109@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=jfbeam@bluetronic.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul@clubi.ie \
    /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).