From: Jeff Garzik <jgarzik@pobox.com>
To: "Daniel B." <dsb@smart.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE DMA errors, massive disk corruption: Why? Fixed Yet? Why not re-do failed op?
Date: Mon, 06 Oct 2003 17:26:53 -0400 [thread overview]
Message-ID: <3F81DE1D.6070304@pobox.com> (raw)
In-Reply-To: <3F81D995.D9C13F33@smart.net>
Daniel B. wrote:
> If the kernel starts a write command for block 993, wouldn't it wait
> for a DMA interrupt signalling that the drive has received and accepted
> the command before the kernel starts the write command for block 10934?
With command queueing, no, it would not wait.
> If it timed out waiting for that interrupt, can't it re-issue the
> write for block 993 before proceeding?
Assuming a large amount of sanity in your OS driver... certainly.
Jeff
next prev parent reply other threads:[~2003-10-06 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-06 19:32 IDE DMA errors, massive disk corruption: Why? Fixed Yet? W hy " Mudama, Eric
2003-10-06 20:20 ` IDE DMA errors, massive disk corruption: Why? Fixed Yet? Why " Daniel B.
2003-10-06 20:45 ` Valdis.Kletnieks
2003-10-06 21:07 ` Daniel B.
2003-10-06 21:26 ` Jeff Garzik [this message]
2003-10-07 5:24 ` IDE DMA errors, massive disk corruption: Why? Fixed Yet? Whynot " Daniel B.
2003-10-07 6:03 ` Valdis.Kletnieks
2003-10-07 12:23 ` Ruth Ivimey-Cook
2003-10-07 13:46 ` IDE DMA errors, massive disk corruption: Why? Fixed Yet? Whynotre-do " Daniel B.
2003-10-07 13:32 ` IDE DMA errors, massive disk corruption: Why? Fixed Yet? Why not re-do " Daniel B.
2003-10-10 1:10 ` IDE DMA errors, massive disk corruption: Why? Fixed Yet? W hy " Greg Stark
-- strict thread matches above, loose matches on Subject: below --
2003-10-06 18:42 IDE DMA errors, massive disk corruption: Why? Fixed Yet? Why " Daniel B.
2003-10-06 19:11 ` 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=3F81DE1D.6070304@pobox.com \
--to=jgarzik@pobox.com \
--cc=dsb@smart.net \
--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
Powered by JetHome