From: yodaiken@fsmlabs.com
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: yodaiken@fsmlabs.com, Mark Hounschell <markh@compro.net>,
"Wessler, Siegfried" <Siegfried.Wessler@de.hbm.com>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: interrupt latency
Date: Wed, 28 Aug 2002 07:53:19 -0600 [thread overview]
Message-ID: <20020828075319.A24146@hq.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020828080308.14759A-101000@chaos.analogic.com>; from root@chaos.analogic.com on Wed, Aug 28, 2002 at 08:18:25AM -0400
On Wed, Aug 28, 2002 at 08:18:25AM -0400, Richard B. Johnson wrote:
> No, no, no. There is no such port read that takes 18 microseconds, even
> on old '386 machines with real ISR slots. A port read on those took
> almost exactly 300 nanoseconds and, in fact, was the limiting factor
> for the programmed I/O devices on the ISA bus.
Amazing how they can do that with a bus clock that is much slower -)
--
---------------------------------------------------------
Victor Yodaiken
Finite State Machine Labs: The RTLinux Company.
www.fsmlabs.com www.rtlinux.com
next prev parent reply other threads:[~2002-08-28 13:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 9:58 Wessler, Siegfried
2002-08-27 14:11 ` Stephen Samuel
2002-08-27 17:16 ` Robert Schwebel
2002-08-27 21:44 ` Stephen Samuel
2002-08-27 17:41 ` Mark Hounschell
2002-08-27 18:01 ` Richard B. Johnson
2002-08-27 19:54 ` yodaiken
2002-08-27 20:44 ` Richard B. Johnson
2002-08-27 20:56 ` yodaiken
2002-08-27 22:47 ` Rogier Wolff
2002-08-28 12:18 ` Richard B. Johnson
2002-08-28 13:41 ` yodaiken
2002-08-28 14:25 ` Jonathan Lundell
2002-08-28 13:53 ` yodaiken [this message]
2002-08-28 15:02 ` Richard B. Johnson
2002-08-28 15:19 ` yodaiken
2002-08-28 15:31 ` Alan Cox
2002-08-28 15:37 ` Richard B. Johnson
2002-08-28 16:53 ` Randy.Dunlap
2002-08-28 12:42 ` Pavel Machek
2002-08-27 18:05 ` Dag Nygren
2002-10-30 23:50 Keith Adamson
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=20020828075319.A24146@hq.fsmlabs.com \
--to=yodaiken@fsmlabs.com \
--cc=Siegfried.Wessler@de.hbm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®