From: Chr <chunkeey@web.de>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: Thorsten Leemhuis <thl@ct.heise.de>,
Thorsten Leemhuis <fedora@leemhuis.info>,
Chuck Ebbert <cebbert@redhat.com>, Jeff Garzik <jeff@garzik.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2.6.22-rc6] ATA: add a PCI ID for Intel Santa Rosa PATA controller
Date: Fri, 6 Jul 2007 21:45:01 +0200 [thread overview]
Message-ID: <200707062145.01928.chunkeey@web.de> (raw)
In-Reply-To: <39B20DF628532344BC7A2692CB6AEE070181E0EA@orsmsx420.amr.corp.intel.com>
On Friday, 6. July 2007, Gaston, Jason D wrote:
> >> > On the other hand, we can leave it, because of a
> >"off-by-one error" in ata_piix.c,
> >> > do_pata_set_dmamode, line ~770:
> >> > [...]
> >>
> >
> >Thanks,
> > Chr.
> >
> >
>
> I quickly tried this patch on an ICH7-R system with an ATA133 Maxtor HD
> and it did not seem to do anything bad. I see no difference in function
> or performance with the patch.
>
> Jason
>
Thanks for testing, but you forgot some numbers. ;)
(bonnie++? hdparm -i && hdparm -t...)
Because, I don't think that Maxtor HD's mechanics is faster than 100MB/s..
The only thing that can keep up with > 100MB/s are the few MB of Cache on every HDD...
(so, does anyone have a good idea to check the HDD's cache performance?
hdparm -t reads too much data)
I came up with something like:
"dd if=/dev/sdX of=/dev/null bs=4M count=1 iflag=direct"
and run it 10 times in a row.
here's a test run with a SATA I WD2500YD-01N ( hdparm -t performance: ~57MB/s)
4194304 bytes (4.2 MB) copied, 0.0897687 seconds, 46.7 MB/s
4194304 bytes (4.2 MB) copied, 0.0776731 seconds, 54.0 MB/s
4194304 bytes (4.2 MB) copied, 0.0711224 seconds, 59.0 MB/s
4194304 bytes (4.2 MB) copied, 0.0679675 seconds, 61.7 MB/s
4194304 bytes (4.2 MB) copied, 0.0603272 seconds, 69.5 MB/s
4194304 bytes (4.2 MB) copied, 0.0543068 seconds, 77.2 MB/s
4194304 bytes (4.2 MB) copied, 0.0522881 seconds, 80.2 MB/s
4194304 bytes (4.2 MB) copied, 0.0520612 seconds, 80.6 MB/s
4194304 bytes (4.2 MB) copied, 0.0444805 seconds, 94.3 MB/s
4194304 bytes (4.2 MB) copied, 0.0338407 seconds, 124 MB/s
4194304 bytes (4.2 MB) copied, 0.0333174 seconds, 126 MB/s
Thanks,
Chr
next prev parent reply other threads:[~2007-07-06 19:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 19:16 ATA: add a PCI ID for Intel Santa Rosa PATA controller Chuck Ebbert
2007-06-28 19:47 ` [patch 2.6.22-rc6] " Chuck Ebbert
2007-06-29 14:31 ` Jeff Garzik
2007-07-02 5:02 ` Thorsten Leemhuis
2007-07-02 9:07 ` Thorsten Leemhuis
2007-07-02 11:24 ` Chr
2007-07-02 11:44 ` Thorsten Leemhuis
2007-07-02 14:36 ` Chr
2007-07-04 14:03 ` Thorsten Leemhuis
2007-07-05 20:30 ` Chr
2007-07-06 19:06 ` Gaston, Jason D
2007-07-06 19:45 ` Chr [this message]
2007-07-06 20:01 ` Thorsten Leemhuis
2007-07-06 20:43 ` Jeff Garzik
2007-07-05 21:17 ` Alan Cox
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=200707062145.01928.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cebbert@redhat.com \
--cc=fedora@leemhuis.info \
--cc=jason.d.gaston@intel.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thl@ct.heise.de \
/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).