From: Marcin Dalecki <dalecki@evision.ag>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
martin@dalecki.de,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Safety of IRQ during i/o
Date: Fri, 26 Jul 2002 02:34:04 +0200 [thread overview]
Message-ID: <3D4098FC.3080209@evision.ag> (raw)
In-Reply-To: Pine.LNX.3.96.1020725071201.10698A-100000@gatekeeper.tmr.com
Bill Davidsen wrote:
> On 25 Jul 2002, Alan Cox wrote:
>
>
>>There are also some older systems where if the block transfer of the IDE
>>data didn't keep up with the controller instead of handshaking properly
>>it kind of dribbled random numbers onto the disk.
>>
>>Unless anyone knows of PCI era devices with this problem I would be
>>inclined to agree that we should default to IRQ unmasking in the 2.5 IDE
>>code if the IDE controller is PCI.
>
>
> Certainly if the controller is running in DMA mode. If running in PIO mode
> I would think you could still have a problem if the transfer was stopped
> mid-block. Perhaps I'm paranoid, is that a "can't happen" now?
Please note that with the advent of on target device caching this is
neraly impossible unless you chook the cabling - which is of course
something we can't prevent.
>>For old ISA/VLB controllers its safer left as is, and nobody running a
>>machine like that can realistically expect good performance without hand
>>tuning stuff anyway
>
>
> I would think the guts of PIO block transfer would have to be protected
> anyway, but that's a very small part of the code.
next prev parent reply other threads:[~2002-07-26 4:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1027541521.16533.linux-kernel2news@redhat.com>
2002-07-24 22:37 ` Safety of IRQ during i/o Pete Zaitcev
2002-07-24 22:42 ` Bartlomiej Zolnierkiewicz
2002-07-25 7:54 ` Marcin Dalecki
2002-07-25 10:26 ` Alan Cox
2002-07-25 9:34 ` Marcin Dalecki
2002-07-25 11:15 ` Roger Larsson
2002-07-25 11:17 ` Bill Davidsen
2002-07-26 0:34 ` Marcin Dalecki [this message]
2002-07-24 19:58 Bill Davidsen
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=3D4098FC.3080209@evision.ag \
--to=dalecki@evision.ag \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@dalecki.de \
--cc=zaitcev@redhat.com \
/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