From: Jeff Garzik <jgarzik@pobox.com>
To: Julien Didron <jdidron@tripnotik.dyndns.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH try3] a better Silicon Image SATA mod15 write fix?
Date: Mon, 15 Mar 2004 14:14:28 -0500 [thread overview]
Message-ID: <40560094.2040800@pobox.com> (raw)
In-Reply-To: <40560C0E.7060500@tripnotik.dyndns.org>
Julien Didron wrote:
> Hello list,
>
> This driver works :o)
> running hdparm gives those results :
> Timing buffered disk reads: 170 MB in 3.00 seconds = 56.60 MB/sec
> (with 2.6.4-bk4 and sata_sil.c try 3)
> Timing buffered disk reads: 170 MB in 3.01 seconds = 56.56 MB/sec
> (with 2.6.4-mm2)
Thanks much for testing. Try3 had a nasty bug, though.
Can you test Try4 as well?
Regards and thanks again,
Jeff
next prev parent reply other threads:[~2004-03-15 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 15:48 [PATCH] a better Silicon Image SATA mod15 write fix? Jeff Garzik
2004-03-15 18:00 ` Jeff Garzik
2004-03-15 18:04 ` [PATCH try3] " Jeff Garzik
2004-03-15 20:03 ` Julien Didron
2004-03-15 19:14 ` Jeff Garzik [this message]
2004-03-15 19:03 ` [PATCH try4] " Jeff Garzik
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=40560094.2040800@pobox.com \
--to=jgarzik@pobox.com \
--cc=jdidron@tripnotik.dyndns.org \
--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).