From: Tomasz Chmielewski <mangoo@interia.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: poor SATA performance under 2.6.11 (with < 2.6.11 is OK)?
Date: Fri, 15 Apr 2005 00:08:15 +0200 [thread overview]
Message-ID: <425EE9CF.4030202@interia.pl> (raw)
In-Reply-To: <20050414165535.GA15440@irc.pl>
Tomasz Torcz wrote:
> On Thu, Apr 14, 2005 at 06:23:30PM +0200, Tomasz Chmielewski wrote:
>
>>I have a Silicon Image SIL3112A SATA PCI controller + 2x 200GB, 8MB
>>Barracuda drives.
>
>
> Bad combination.
OK, from the link you gave I can see that there might be some problems
with SIL3112 controller + seagate disks...
>>The performance under 2.6 kernels is *very* poor (Timing buffered disk
>>reads never more than 20 MB/sec); under 2.4 it runs quite fine (Timing
>>buffered disk reads around 60 MB/sec).
>
>
> 2.4 risk data corruption. 2.6 sata_sil.c contains blacklist for some
> driver-controller combination.
>
> See: http://home-tj.org/m15w/
...but this link just doesn't explain why performance is sooo bad with
2.6.11.x kernels (Timing buffered disk reads at 10-20 MB/sec), and is
just OK with older 2.6 kernels (Timing buffered disk reads even at about
100 MB/sec with 2.6.8.1).
any clue?
or should I wait for 2.6.11.7 (?), where it should be corrected?
Tomek
next prev parent reply other threads:[~2005-04-14 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 16:23 poor SATA performance under 2.6.11 (with < 2.6.11 is OK)? Tomasz Chmielewski
2005-04-14 16:55 ` Tomasz Torcz
2005-04-14 22:08 ` Tomasz Chmielewski [this message]
2005-04-14 22:34 ` Chris Wright
2005-04-15 7:24 ` Tomasz Chmielewski
2005-04-15 7:32 ` Andre Bender
2005-04-15 11:07 ` Tomasz Chmielewski
2005-04-14 23:03 ` Tomasz Torcz
2005-04-15 7:21 ` Tomasz Chmielewski
-- strict thread matches above, loose matches on Subject: below --
2005-04-14 16:23 Tomasz Chmielewski
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=425EE9CF.4030202@interia.pl \
--to=mangoo@interia.pl \
--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