public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Kirk Wood <cpt.kirk@1tree.net>
To: Speakup List <speakup@braille.uwo.ca>
Subject: Re: A more complete log about my disk access errors
Date: Sun, 3 Jun 2001 08:48:53 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0106030839411.5997-100000@ignatious> (raw)
In-Reply-To: <20010603142214.C16596@joana.gotss.eu.org>

On Sun, Jun 03, 2001 at 12:14:09AM +0200, Victor Tsaran wrote:
> OK, if it turns out that I was fooled by Windows during all this time,
> do you know of any parameter which I could use to tell Linux to fall to
> PIO mode right away?

One way to keep it from ever going into UDMA mode is to remove the support
in the kernel. If you don't compile it in, it won't kick in. (Yes, it can
work on the obvious.) Regardless of the settings, the standard macroslop
and intel have pushed is that the drive starts in PIO mode at boot and
switches when the 32 bit drivers send the signal.

The better cables could be a large factor. I would recomend going with the
shortest possible and if you only use one drive, get a cable without the
connector for the second drive. The second conductor is there to help keep
the good signal in the cable and the bad signal out of the cable. 

When looking at the performance issues, the reality is that you will only
see a morginal increase in speed. While UDMA raises the speed of data
transfer across the wire considerably, this will only happen if the data
requested is in the hardware cache of the drive (and all drives have
this). If there is a miss, or sustained transfer the rate will max out
arround 7 MB per second. (This lower rate is the rate of transfer to and
from the medium.) This is why RAID can increas speeds so dramatically. It
will read the data from multiple drives at once.

=======
Kirk Wood
Cpt.Kirk@1tree.net

Nothing is hard if you know the answer or are used to doing it.




  reply	other threads:[~ UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Victor Tsaran
 ` Gregory Nowak
   ` Victor Tsaran
     ` Kirk Wood
     ` Gregory Nowak
     ` Kerry Hoath
     ` Shaun Oliver
       ` Kirk Wood
         ` Shaun Oliver
   ` Kirk Wood
 ` Kirk Wood
   ` Victor Tsaran
     ` Kerry Hoath
       ` Kirk Wood [this message]
       ` Victor Tsaran
   ` Kerry Hoath
     ` Shaun Oliver
     ` Victor Tsaran
       ` Kerry Hoath
     ` John Covici
       ` Victor Tsaran
 ` Shaun Oliver

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=Pine.LNX.4.21.0106030839411.5997-100000@ignatious \
    --to=cpt.kirk@1tree.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).