From: "James Turinsky" <lkml@SomeSites.com>
To: "Mark Hahn" <hahn@coffee.psychology.mcmaster.ca>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Jens Axboe" <axboe@suse.de>, <andre@linux-ide.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [patch]: ide dma timeout retry in pio
Date: Mon, 28 May 2001 18:11:05 -0400 [thread overview]
Message-ID: <002101c0e7c3$18cdbfb0$0100a8c0@SomeSites.com> (raw)
In-Reply-To: <E154UJT-0003XV-00@the-village.bc.nu>
----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Mark Hahn" <hahn@coffee.psychology.mcmaster.ca>
Cc: "Jens Axboe" <axboe@suse.de>; <andre@linux-ide.org>;
<alan@lxorguk.ukuu.org.uk>; <linux-kernel@vger.kernel.org>
Sent: Monday, May 28, 2001 5:12 PM
Subject: Re: [patch]: ide dma timeout retry in pio
> > really? do we know the nature of the DMA engine problem well
enough?
>
> I can categorise some of them:
>
> 1. Hardware that just doesnt support it.
> 2. Timeouts that are false positives caused by disks having problems
> and being very slow to recover
> 3. Bad cabling
> 4. Stalls caused by heavy PCI traffic
>
> > is there a reason to believe that it'll work better "later"?
>
> #1 will go fail, fail, fail -> PIO now (or should do Im about to try
it)
> #2 and #4 will be transient
> #3 could go either way
Where does the "'DMA Timeout -> disable DMA' then lose all
responsiveness when I issue 'hdparm -d1' while it tries and fails to
re-enable DMA" fit in? The disk will happily run for several days in
UDMA33 and then at some point it craps out with a DMA timeout which
results 1) DMA being turned off and 2) all attempts to re-enable DMA
failing?
And what's up with this:
[root@MoveAlong james]# hdparm /dev/hda
/dev/hda:
multcount = 0 (off)
I/O support = 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 1 (on)
keepsettings = 1 (on)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 19590/16/63, sectors = 19746720, start = 0
[root@MoveAlong james]# hdparm -tT /dev/hda
/dev/hda:
Timing buffer-cache reads: 128 MB in 6.98 seconds = 18.34 MB/sec
Timing buffered disk reads: 64 MB in 5.77 seconds = 11.09 MB/sec
Hmm.. suspicious results: probably not enough free memory for a proper
test.
[root@MoveAlong james]# free
total used free shared buffers
cached
Mem: 126800 123460 3340 0 67284
41572
-/+ buffers/cache: 14604 112196
Swap: 394624 32816 361808
I used to get ~33MB/sec on buffer-cache and ~10MB/sec on buffered disk
reads in 2.2...
--JT
next prev parent reply other threads:[~2001-05-28 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-28 18:34 [patch]: ide dma timeout retry in pio Jens Axboe
2001-05-28 19:39 ` Mark Hahn
2001-05-28 20:13 ` Christopher B. Liebman
2001-05-28 20:37 ` Jens Axboe
2001-05-28 22:15 ` Andre Hedrick
2001-05-28 22:26 ` Jens Axboe
2001-05-29 0:09 ` Andre Hedrick
2001-05-29 0:30 ` Jens Axboe
2001-05-28 21:12 ` Alan Cox
2001-05-28 22:11 ` James Turinsky [this message]
2001-05-29 6:18 ` Larry McVoy
2001-05-28 22:20 ` Alan Cox
2001-05-28 22:56 ` Meelis Roos
2001-05-29 7:11 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2001-05-30 21:09 Diefenbaugh, Paul S
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='002101c0e7c3$18cdbfb0$0100a8c0@SomeSites.com' \
--to=lkml@somesites.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=axboe@suse.de \
--cc=hahn@coffee.psychology.mcmaster.ca \
--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