From: Tomasz Torcz <zdzichu@irc.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 01:03:17 +0200 [thread overview]
Message-ID: <20050414230317.GA12156@irc.pl> (raw)
In-Reply-To: <425EE9CF.4030202@interia.pl>
On Fri, Apr 15, 2005 at 12:08:15AM +0200, Tomasz Chmielewski wrote:
> >>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?
The sata_sil blacklist grown over time. Older version didn't mark your
drive as bad. Check sata_sil history at
http://www.linuxhq.com/kernel/file/drivers/scsi/sata_sil.c ,
you may find exact time when your drive got blacklisted.
--
Tomasz Torcz To co nierealne - tutaj jest normalne.
zdzichu@irc.-nie.spam-.pl Ziomale na życie mają tu patenty specjalne.
next prev parent reply other threads:[~2005-04-14 23:03 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
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 [this message]
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=20050414230317.GA12156@irc.pl \
--to=zdzichu@irc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.