From: Tejun Heo <htejun@gmail.com>
To: Soeren Sonnenburg <kernel@nn7.de>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: seagate disks on sil3114 - slow?
Date: Fri, 26 Oct 2007 11:32:51 +0900 [thread overview]
Message-ID: <472151D3.6060403@gmail.com> (raw)
In-Reply-To: <1192697546.5720.51.camel@localhost>
Soeren Sonnenburg wrote:
> On Thu, 2007-10-18 at 01:07 -0400, Jeff Garzik wrote:
>> Soeren Sonnenburg wrote:
>>> Dear all,
>>>
>>> I just now realize that all disk i.o. on my machine is quite slow
>>> compared with the pata disks I had before. Furthermore I recognized that
>>> I only have seagates (ST3400832AS,ST3400620AS,ST3750640AS,ST3750640AS)
>>> connected to a sil3114 controller.
>>>
>>> Being on kernel 2.6.23.1 and stumbling across
>>> http://home-tj.org/wiki/index.php/Sil_m15w I am now wondering if this
>>> patch made it already in kernel (or when it will make it if it is not
>>> yet in/why never).
>> Are you sure you have a 3114? the mod15write isn't applied to that chip.
>> Does your dmesg say "applying Seagate errata fix (mod15write workaround)" ?
>
> At least lspci / dmesg indicates I have a 3114 ... but maybe the problem
> is something else. Is there a raw device speed, readonly benchmark to
> check whether things are as expected?
"dd if=/dev/sdX of=/dev/null bs=1M"? Also, does changing IO scheduler
to deadline make any difference?
--
tejun
next prev parent reply other threads:[~2007-10-26 2:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 4:54 seagate disks on sil3114 - slow? Soeren Sonnenburg
2007-10-18 5:07 ` Jeff Garzik
2007-10-18 8:52 ` Soeren Sonnenburg
2007-10-26 2:32 ` Tejun Heo [this message]
2007-10-26 5:49 ` Soeren Sonnenburg
2007-10-26 6:08 ` Tejun Heo
2007-10-27 5:21 ` Soeren Sonnenburg
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=472151D3.6060403@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=kernel@nn7.de \
--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).