linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Ricky Beam <jfbeam@bluetronic.net>
Cc: linux-ide@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix sata_sil quirk
Date: Tue, 22 Jun 2004 18:12:38 -0400	[thread overview]
Message-ID: <40D8AED6.8050503@pobox.com> (raw)
In-Reply-To: <Pine.GSO.4.33.0406221620300.25702-200000@sweetums.bluetronic.net>

Ricky Beam wrote:
> On Tue, 22 Jun 2004, Jeff Garzik wrote:
> 
>> Here's my suggested fix...  good catch Ricky.
> 
> 
> And I don't even know why I looked at max_sectors :-) (I need more Dew.)
> 
>> Yes, unfortunately performance will be dog slow.
> 
> 
> Well, at least puppy slow...
> Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
> sda            1811.65         0.00      9629.85          0     577887
> sdb            1807.15         0.00      9629.60          0     577872
> sdc            1807.25         0.00      9629.86          0     577888
> sdd            1807.05         0.00      9629.86          0     577888
> md_d0         14444.64         0.00     48148.84          0    2889412
> md_d0p2        9629.78         0.00     38519.11          0    2311532
> (over 60sec,  8M O_DIRECT accesses, 128 stripes * 16k RAID0)
> 
> Without the MOD15 hack, the numbers are 2x higher, but they stop after
> a few minutes :-)

Is this with my patch?

If so, I'll go ahead and forward it upstream, since I would certainly 
like a stabilization fix applied ASAP.


>> I've got contacts at Silicon Image, and have been meaning to bug them
>> for a "real fix" for a while.  It is rumored that there is a much better
>> fix, which allows full performance while at the same time not killing
>> your SATA drive due to odd-sized SATA frames on the wire.
> 
> 
> Ask them what they do in their driver? (the linux one and the windows one)
> Looking at the linux driver, the mod15 quirk is there, but there doesn't
> appear to be any associated device list. (I've already post the single
> Maxtor device listed.)  FreeBSD detects the stall, resets the chip and
> hopes that clears the problem. (People are not happy about that.)

The full-speed fix requires splitting affected DMA writes into two 
separate commands, when the sector count matches "sectors % 15 == 1".

	Jeff



  parent reply	other threads:[~2004-06-22 22:12 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 [this message]
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

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=40D8AED6.8050503@pobox.com \
    --to=jgarzik@pobox.com \
    --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).