public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gunther.Mayer@t-online.de (Gunther Mayer)
To: Andre Hedrick <andre@linux-ide.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: (ide.2.2.19.04092001.patch:) DiskPerf compile problem
Date: Tue, 10 Apr 2001 21:23:43 +0200	[thread overview]
Message-ID: <3AD35DBF.168DD54@t-online.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10104091720030.1878-100000@master.linux-ide.org>

Andre Hedrick wrote:
> 
...
> DiskPerf /dev/hde
> Device: IBM-DTLA-307075 Serial Number: YSDYSFA5874
> LBA 0 DMA Read Test                      = 63.35 MB/Sec (3.95 Seconds)
> Outer Diameter Sequential DMA Read Test  = 35.89 MB/Sec (6.97 Seconds)
> Inner Diameter Sequential DMA Read Test  = 17.64 MB/Sec (14.17 Seconds)

Where can I get the latest DiskPerf?

The version on:
http://www.xx.kernel.org/pub/linux/kernel/people/hedrick/utility-patches/DiskPerf-1.0.1.tar.gz
does not compile at all:

linux:~/DiskPerf-1.0 # make
gcc -o DiskPerf -O3 -lglib DiskPerf.c
DiskPerf.c: In function `ataRead':
DiskPerf.c:155: storage size of `reqtask' isn't known
DiskPerf.c:156: storage size of `taskfile' isn't known
DiskPerf.c:157: `ide_reg_valid_t' undeclared (first use in this function)
...

  reply	other threads:[~2001-04-10 19:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-10  0:33 ide.2.2.19.04092001.patch Andre Hedrick
2001-04-10 19:23 ` Gunther Mayer [this message]
2001-04-12 22:03   ` (ide.2.2.19.04092001.patch:) DiskPerf compile problem Andre Hedrick
2001-04-11  5:35 ` ide.2.2.19.04092001.patch Shane Wegner
2001-04-11  5:46   ` ide.2.2.19.04092001.patch William Park
2001-04-12 22:05   ` ide.2.2.19.04092001.patch Andre Hedrick
2001-04-12 22:11     ` ide.2.2.19.04092001.patch Shane Wegner
2001-04-12 22:19       ` ide.2.2.19.04092001.patch Andre Hedrick

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=3AD35DBF.168DD54@t-online.de \
    --to=gunther.mayer@t-online.de \
    --cc=andre@linux-ide.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