linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: "Oliver.Korpilla@gmx.de" <Oliver.Korpilla@gmx.de>,
	kiu <kiu@gmx.net>,
	linux-ide@vger.kernel.org
Subject: Re: kernel history of ide performance
Date: Wed, 13 Apr 2005 14:57:53 -0400	[thread overview]
Message-ID: <425D6BB1.1040904@rtr.ca> (raw)
In-Reply-To: <58cb370e050405021470f3a851@mail.gmail.com>

Note that hdparm has a "--direct" flag to perform O_DIRECT I/O,
which can sometimes give different information than the default method.

But the one weakness with 'hdparm -t' in either case,
is that it performs a single READ at a time, rather than
queuing up a pipeline full of READs.  So it should always
slightly under report achievable throughput.

Cheers


      parent reply	other threads:[~2005-04-13 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05  8:46 kernel history of ide performance kiu
2005-04-05  9:00 ` Bartlomiej Zolnierkiewicz
2005-04-05  9:02 ` Oliver.Korpilla
2005-04-05  9:14   ` Bartlomiej Zolnierkiewicz
2005-04-05  9:34     ` kiu
2005-04-13 18:57     ` Mark Lord [this message]

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=425D6BB1.1040904@rtr.ca \
    --to=liml@rtr.ca \
    --cc=Oliver.Korpilla@gmx.de \
    --cc=bzolnier@gmail.com \
    --cc=kiu@gmx.net \
    --cc=linux-ide@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).