public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: Christoph Pleger <Christoph.Pleger@cs.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATA-disk named sda
Date: Sat, 07 Jul 2007 23:40:33 +0200	[thread overview]
Message-ID: <46900851.4060403@gmail.com> (raw)
In-Reply-To: <20070706143055.01aa9ef6.Christoph.Pleger@cs.uni-dortmund.de>

On 07/06/2007 02:30 PM, Christoph Pleger wrote:

> And what about hdparm (setting 32bit I/O and multi-sector mode)? Suren 
> wrote that 32bit I/O makes no sense when using DMA. Maybe that's right, 
> but it does not correspond with my experiences. At least, I have the 
> "feeling" that my IDE disks work much faster since I enabled 32bit 
> support (DMA already was on before).

hdparm -t /dev/hda (or /dev/sda -- it works for the SD interface as well) is 
a quick test of a drive's sequential read speed.

I have, at the time, noticed at least on older controllers/drives (Intel 430 
generation chipsets with things like 8G UDMA33 disks) that I could reliably 
increase the result with something like 1MB/s (to a total of 6 to 8, so it 
wasn't insignificant) by enabling 32-bit I/O. Had also understood that it 
shouldn't make a difference with DMA, but just went "oh well" and stuck a 
"hdparm -c1" in my bootup scripts.

(if anyone tries; note that hdparm -a can have a large effect on that result 
as well on some setups -- on machines where it does, -a 1024 usually gives 
me best results)

Rene.

  parent reply	other threads:[~2007-07-07 21:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06  8:21 PATA-disk named sda Christoph Pleger
2007-07-06  9:13 ` Suren Karapetyan
2007-07-06  9:36   ` Christoph Pleger
2007-07-06  9:58     ` Suren Karapetyan
2007-07-06 17:55     ` Mark Lord
2007-07-07 18:33       ` Jan Engelhardt
2007-07-06  9:52 ` Alejandro Riveira Fernández
2007-07-06 10:11 ` Uwe Kiewel
2007-07-06 10:18 ` Alan Cox
2007-07-06 12:30   ` Christoph Pleger
2007-07-06 14:40     ` Gabriel C
2007-07-06 15:19     ` Alan Cox
2007-07-07 21:40     ` Rene Herman [this message]
     [not found] <fa.VMMtK2yPXE5gkxuIC8MWb1aPBiQ@ifi.uio.no>
     [not found] ` <fa.23lYEA4r0kfTVDJ1AKcxSE4vGKA@ifi.uio.no>
     [not found]   ` <fa.DRDWDh+VAXx84D/6XHgY6h2wB+E@ifi.uio.no>
2007-07-06 14:39     ` Robert Hancock
2007-07-06 17:58       ` Mark Lord
2007-07-06 18:47         ` Bartlomiej Zolnierkiewicz
2007-07-06 18:09       ` Bartlomiej Zolnierkiewicz

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=46900851.4060403@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=Christoph.Pleger@cs.uni-dortmund.de \
    --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