From: bl0 <bl0-052@playker.info>
To: linux-ide@vger.kernel.org
Cc: linux-pci@vger.kernel.org
Subject: Re: sata_sil data corruption, possible workarounds
Date: Thu, 20 Dec 2012 09:54:32 +0100 [thread overview]
Message-ID: <kaujmk$op$1@ger.gmane.org> (raw)
In-Reply-To: 50D13831.9040105@gmail.com
On Wednesday 19 December 2012 04:44, Robert Hancock wrote:
> On 12/18/2012 09:23 AM, bl0 wrote:
>> Do you think something should be done about it in the linux sata_sil
>> driver? For a lack of a better solution, here is my suggestion. There is
>> already one option 'slow_down' for problematic disks. Another option, for
>> example 'cache_line_workaround', could be added for problematic
>> motherboards. If enabled, the most straightforward way is to set cache
>> line size to 0 and not worry about the fifo_cfg register. If someone else
>> confirms that it solves the problem for them, this option could be
>> enabled automatically if certain motherboard chipset is detected.
>
> We'd have to somehow narrow down which chipsets were involved, which
> might be a hard task. Do you have an idea of how much the performance is
> hurt by these workarounds? If it's not a lot, it might make sense to do
> it by default.
After setting cache line size to 0, write speed as shown by 'dd
if=/tmpfs/testfile of=/dev/sdc9 bs=1M count=256' goes down from about
45 MB/s to 17 MB/s. Personally I don't care about performance, reliability
and data safety are more important to me.
The other workaround is to increase cache line size to 64 bytes, if
necessary, and set fifo_cfg to 0. No difference in performance measured.
This workaround is more of a hit or miss. It seems to contradict that code
commit made back in 2005, which was also about data corruption. In the
worst case, what solves data corruption problem on some motherboards might
introduce this problem on some other motherboards.
next prev parent reply other threads:[~2012-12-20 8:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-15 8:02 sata_sil data corruption, possible workarounds bl0
2012-12-15 21:55 ` Robert Hancock
2012-12-16 12:21 ` bl0
2012-12-17 5:44 ` Robert Hancock
2012-12-18 15:23 ` bl0
2012-12-19 3:44 ` Robert Hancock
2012-12-20 8:54 ` bl0 [this message]
2013-01-07 4:11 ` Robert Hancock
2013-01-08 12:25 ` bl0
2012-12-24 14:37 ` bl0
2013-01-09 4:48 ` Robert Hancock
2013-01-09 19:17 ` Tejun Heo
2013-01-11 10:28 ` bl0
2013-01-11 13:53 ` Mark Lord
2013-01-11 13:54 ` Mark Lord
2013-01-14 17:58 ` Jeff Garzik
2013-01-15 7:44 ` bl0
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='kaujmk$op$1@ger.gmane.org' \
--to=bl0-052@playker.info \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pci@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