public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: quintaq@yahoo.co.uk
To: <linux-kernel@vger.kernel.org>
Subject: Re: UDMA 100 / PIIX4 question
Date: Tue, 20 Mar 2001 20:21:41 +0000	[thread overview]
Message-ID: <20010320202020Z130768-406+2207@vger.kernel.org> (raw)
In-Reply-To: <3AB79464.A7A95A54@coplanar.net>
In-Reply-To: <20010318165246Z131240-406+1417@vger.kernel.org> <3AB65C51.3DF150E5@bigfoot.com> <3AB65F14.26628BEF@coplanar.net> <20010319222113Z131588-406+1752@vger.kernel.org> <3AB7811D.97601E82@internet-factory.de> <3AB79464.A7A95A54@coplanar.net>

Hi,

First, thank you very much Mark, Tim, Jeremy and Holger for your continuing contributions which, I think, are at last casting some light on my "problem".

> Yes this is why I originally replied to the post... but he's not using a
> PIIXx at
> all,
> but the IDE chip on an Intel 815 motherboard.  I'm not sure if they use
> the same
> driver
> , but I don't think so.
> 

I found a helpful post from Peter Denison on 6th January this year which suggests that it is at least the same driver.

"Description:
Includes new PCI device IDs for the Intel i815E chipset, and corrects some
of the names for the associated parts of the chipset. This has effects in
the EEPro100 network driver and the PCI IDE driver.
Detail & Justification:
The Intel ICH2 (I/O Controller Hub 2) is used in several chipsets, not
just the 820 (Camino) chipset it is accredited to in the PCI ID database.
Nor is the IDE portion of the ICH2 really a PIIX4 chip, though it is very
similar and PIIX driver works on both. These changes are just
internal macro naming and minor user interface tweaks."


> try hdparm -t /dev/hda1 instead of hda5 (if those are on opposite ends
> of the
> disk)
> 
> include output of fdisk so we can see partition layout, and results of
> hdparm on
> different areas.

Here is my fdisk output :

Disk /dev/hda: 255 heads, 63 sectors, 3737 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hda1   *         1       932   7486258+   b  Win95 FAT32
/dev/hda2           933      3737  22531162+   5  Extended
/dev/hda5           933       935     24066   83  Linux
/dev/hda6           936       952    136521   82  Linux swap
/dev/hda7           953      3737  22370481   83  Linux


I also ran hdparm -tT /dev/hda1:
 
Timing buffer-cache reads:   128 MB in  1.28 seconds =100.00 MB/sec
 Timing buffered disk reads:  64 MB in  4.35 seconds = 14.71 MB/sec

Which obviously gives much the same result as my usual hdparm -tT /dev/hda

I then tried hdparm -tT /dev/hda7:

 Timing buffer-cache reads:   128 MB in  1.28 seconds =100.00 MB/sec
 Timing buffered disk reads:  64 MB in  2.12 seconds = 30.19 MB/sec

As you would expect, I get almost identical results with several repetitions.

Does this solve the mystery ?

Regards,

Geoff

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


  reply	other threads:[~2001-03-20 20:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-18 16:53 UDMA 100 / PIIX4 question quintaq
2001-03-19 19:21 ` Tim Moore
2001-03-19 19:33   ` Jeremy Jackson
2001-03-19 20:17     ` Tim Moore
2001-03-19 22:22       ` quintaq
2001-03-20 16:11         ` Holger Lubitz
2001-03-20 17:33           ` Jeremy Jackson
2001-03-20 20:21             ` quintaq [this message]
2001-03-20 21:32               ` Mark Hahn
2001-03-21  9:56                 ` quintaq
2001-03-21 16:26                   ` quintaq
2001-03-21 16:38                     ` Mike Dresser
2001-03-23 10:27                       ` quintaq
2001-03-21 19:18                   ` Tim Moore
2001-03-21 19:29                   ` Andre Hedrick
2001-03-22 13:21                     ` Holger Lubitz
2001-03-23 10:27                     ` quintaq
2001-03-21 19:14                 ` Tim Moore
2001-03-23 10:27                   ` quintaq
2001-03-23 21:17                     ` Tim Moore
2001-03-21 14:06             ` Holger Lubitz
2001-03-19 20:32     ` Mark Hahn
2001-03-19 21:51       ` Tim Moore
2001-03-19 19:55   ` Jeremy Jackson
2001-03-19 20:38     ` Tim Moore

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=20010320202020Z130768-406+2207@vger.kernel.org \
    --to=quintaq@yahoo.co.uk \
    --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