From: George Georgalis <georgalis@gmail.com>
To: Linux Kernel Mail List <linux-kernel@vger.kernel.org>,
George Georgalis <george@galis.org>
Cc: Ricky Beam <jfbeam@bluetronic.net>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] fix sata_sil quirk
Date: Sun, 26 Sep 2004 23:40:05 -0400 [thread overview]
Message-ID: <d91f4d0c040926204019fde277@mail.gmail.com> (raw)
In-Reply-To: <20040628015431.GA31687@trot.local>
On Sun, 27 Jun 2004 21:54:31 -0400, George Georgalis <george@galis.org> wrote:
> On Wed, Jun 23, 2004 at 02:34:35AM -0400, Ricky Beam wrote:
> >
> >That list needs a:
> > { "ST3160023AS", SIL_QUIRK_MOD15WRITE },
> >as well.
>
> happens to be my drive, is there any way to tell a drive needs
> be in the quirk 15 list, other than it's Seagate and big writes
> block the dev?
Actually my problem with big writes was the bk kernel I downloaded was
a rev too early (2.6.7-bk7 ?).
I tested the sata_sil.c version from June 25 (via bk checkout)
extensively and had no problem... posted my results then, hdparm
reported ~42 - 51 MB/sec, and never a write block.
Today I try putting 2.6.8.1 on the box and I'm getting ~14 MB/sec, the
drive has been added to the sil_blacklist. Why? What did I miss?
I've taken my drive out of the black list, abused it with 5 continuous
writes and "top id 0" no problem after 58Gb. I'm doing it again this
time simultaneously with a massive rm -rf of backup directories. I
really don't anticipate a problem.
So what's up with
/*{ "ST3160023AS", SIL_QUIRK_MOD15WRITE },*/
before it got in there, it was said the black list "would not grow"
(for unexplained reasons).
// George
--
George Georgalis, systems architect, administrator Linux BSD IXOYE
http://galis.org/george/ cell:646-331-2027 mailto:george@galis.org
prev parent reply other threads:[~2004-09-27 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
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 [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=d91f4d0c040926204019fde277@mail.gmail.com \
--to=georgalis@gmail.com \
--cc=george@galis.org \
--cc=jfbeam@bluetronic.net \
--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).