From: Alan <alan@lxorguk.ukuu.org.uk>
To: Mark Lord <mlord@pobox.com>
Cc: Tejun Heo <htejun@gmail.com>,
albertl@mail.com, albertcc@tw.ibm.com,
Jeff Garzik <jeff@garzik.org>,
Linux IDE <linux-ide@vger.kernel.org>,
matthieu castet <castet.matthieu@free.fr>,
Tobias Powalowski <t.powa@gmx.de>
Subject: Re: [PATCH] libata: waits up to 10 microseconds for early irq problem
Date: Tue, 28 Nov 2006 14:12:00 +0000 [thread overview]
Message-ID: <20061128141200.104facf3@localhost.localdomain> (raw)
In-Reply-To: <456C410C.9060604@pobox.com>
On Tue, 28 Nov 2006 09:00:44 -0500
Mark Lord <mlord@pobox.com> wrote:
> Alan, I confess that I really don't understand this example (below).
> Can you try again, with something concrete enough for a rusty old
> IDE hacker to understand?
The asynchronocity isn't at the IDE level - its at the PCI bus level. The
IRQ path between a PCI card and the CPU is not synchronous to I/O cycles.
Alan
next prev parent reply other threads:[~2006-11-28 14:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200611180759.34622.t.powa@gmx.de>
[not found] ` <20061118002357.564dbb9d.akpm@osdl.org>
2006-11-18 21:20 ` possibility to merge via_pata fixes to .19 stable series? Jeff Garzik
2006-11-18 22:43 ` Alan
2006-11-19 3:07 ` Andrew Morton
2006-11-19 5:34 ` Tejun Heo
2006-11-19 6:02 ` Andrew Morton
2006-11-28 6:52 ` [PATCH] libata: waits up to 10 microseconds for early irq problem Albert Lee
2006-11-28 10:25 ` Alan
2006-11-28 10:27 ` Tejun Heo
2006-11-28 10:46 ` Alan
2006-11-28 14:00 ` Mark Lord
2006-11-28 14:12 ` Alan [this message]
2006-11-28 14:16 ` Mark Lord
2006-11-28 11:32 ` Albert Lee
2006-11-28 14:17 ` Albert Lee
2006-11-28 14:42 ` Mark Lord
2006-11-28 19:13 ` Jeff Garzik
2006-11-30 9:43 ` [PATCH] libata: blacklist " Albert Lee
2006-11-30 11:29 ` Alan
2006-11-30 20:37 ` Mark Lord
2006-11-30 20:45 ` Mark Lord
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=20061128141200.104facf3@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=albertl@mail.com \
--cc=castet.matthieu@free.fr \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.com \
--cc=t.powa@gmx.de \
/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 NNTP newsgroup(s).