From: Soeren Sonnenburg <kernel@nn7.de>
To: Tejun Heo <htejun@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: seagate disks on sil3114 - slow?
Date: Sat, 27 Oct 2007 07:21:02 +0200 [thread overview]
Message-ID: <1193462462.7122.7.camel@localhost> (raw)
In-Reply-To: <47218442.4000103@gmail.com>
On Fri, 2007-10-26 at 15:08 +0900, Tejun Heo wrote:
> Soeren Sonnenburg wrote:
> > On Fri, 2007-10-26 at 11:32 +0900, Tejun Heo wrote:
> [...]
> > OK I knew that one... about 50-60M/s - sounds reasonable, but if I
> > understand the m15w problem correctly it can only be triggered on
> > writes...
>
> 3114 -> no m15w problem and m15w doesn't slow down transfers. It locks
> up certain drives. What slows down transfers is workaround for m15w.
Which means Bernd's sil3114 m15w patch does not fix anything but maybe
just lowered pci-bus load. Well....
Soeren
prev parent reply other threads:[~2007-10-27 5:21 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
2007-10-26 5:49 ` Soeren Sonnenburg
2007-10-26 6:08 ` Tejun Heo
2007-10-27 5:21 ` Soeren Sonnenburg [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=1193462462.7122.7.camel@localhost \
--to=kernel@nn7.de \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--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).