From: Jeff Garzik <jeff@garzik.org>
To: Bernd Schubert <bs@q-leap.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] faster workaround
Date: Thu, 11 Oct 2007 11:04:45 -0400 [thread overview]
Message-ID: <470E3B8D.4080002@garzik.org> (raw)
In-Reply-To: <200710111639.38240.bs@q-leap.de>
Bernd Schubert wrote:
> On Thursday 11 October 2007 16:19:37 Jeff Garzik wrote:
>> 1) Just about the only valid optimization is to ensure that only the
>> write path must be limited to small chunks, not both read- and
>> write-paths. Tejun had a patch to do this a long time ago, but it's an
>> open question whether the large amount of code is worth it for a rare
>> combination.
>
> How large? This patch is rather small? Where can I find it?
http://home-tj.org/wiki/index.php/Sil_m15w
> The problem came up, when 200GB drives were replaced by *newer* 250GB drives
> (well maybe not the newest, no idea were they came from).
>
> Anyway, I'm testing for more than 24h already and didn't observe any data
> corruption as without the patch. I know this is only an obersavation and no
> definite prove...
> Also, this is with 3114, maybe this chip behaves a bit different than 3112?
3114 + new SATA drive is definitely a new one for us.
It would help to (a) use the latest kernel, (b) post your .config with
the latest kernel, (c) post lspci booted into latest kernel, and (d)
post dmesg booted into latest kernel.
Jeff
next prev parent reply other threads:[~2007-10-11 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 15:09 sil3114 data corruption Bernd Schubert
2007-10-10 9:12 ` Bernd Schubert
2007-10-11 12:09 ` [PATCHES] " Bernd Schubert
2007-10-11 12:15 ` [PATCH 1/3] " Bernd Schubert
2007-10-11 12:20 ` [PATCH 2/3] " Bernd Schubert
2007-10-11 12:33 ` [PATCH 3/3] faster workaround Bernd Schubert
2007-10-11 13:26 ` Alan Cox
2007-10-11 14:19 ` Jeff Garzik
2007-10-11 14:39 ` Bernd Schubert
2007-10-11 15:04 ` Jeff Garzik [this message]
2007-10-11 15:18 ` Bernd Schubert
2007-10-12 21:08 ` Jeff Garzik
2007-10-15 10:18 ` Bernd Schubert
2007-10-11 14:50 ` Alan Cox
2007-10-11 14:59 ` Jeff Garzik
2007-10-23 8:08 ` Tejun Heo
2007-10-23 17:28 ` Bernd Schubert
2007-10-24 13:39 ` 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=470E3B8D.4080002@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bs@q-leap.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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).