linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <fedora@leemhuis.info>
To: Chr <chunkeey@web.de>
Cc: "Gaston, Jason D" <jason.d.gaston@intel.com>,
	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, 06 Jul 2007 22:01:32 +0200	[thread overview]
Message-ID: <468E9F9C.9010508@leemhuis.info> (raw)
In-Reply-To: <200707062145.01928.chunkeey@web.de>

On 06.07.2007 21:45, Chr wrote:
> 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:
>>>>> [...]
>> 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.
>
> 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?

Something like the good old "Coretest" might come close to it. But I'm
not aware of any linux benchmark out there that has the
coretest-behavior (reading the same 64k block in a loop over and over
again).

But anyway: Sorry, am I the only one that gets nervous if we start to
run a ATA-Hardware (Intels recent ICH southbridges in this case) with a
speed grade (Ultra ATA/133) that is not specified by its manufacturer in
his public data sheets (Ultra ATA/100 max)?

Doing something like that by default would imho be overclocking -- sure,
it works often, but well, it can be the real pita on those systems where
it doesn't. Heck, there is likely not even a real performance advantage
 from Ultra ATA/133 in usual systems with one hard disk per channel, as
most PATA harddisks are afaics not much quicker then round about 70
MByte (and even that only in the early area of the disk).

CU
thl



  reply	other threads:[~2007-07-06 20:02 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
2007-07-06 20:01                     ` Thorsten Leemhuis [this message]
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=468E9F9C.9010508@leemhuis.info \
    --to=fedora@leemhuis.info \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cebbert@redhat.com \
    --cc=chunkeey@web.de \
    --cc=jason.d.gaston@intel.com \
    --cc=jeff@garzik.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).