public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
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 12:42:04 +0000	[thread overview]
Message-ID: <20020828124204.B39@toy.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.3.95.1020827160243.11549A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Aug 27, 2002 at 04:44:34PM -0400

Hi!

> > On Tue, Aug 27, 2002 at 02:01:43PM -0400, Richard B. Johnson wrote:
> > > This cannot be. A stock kernel-2.4.18, running a 133 MHz AMD-SC520,
> > > (like a i586) with a 33 MHz bus, handles interrupts off IRQ7 (the lowest
> > > priority), from the 'printer port' at well over 75,000 per second without
> > > skipping a beat or missing an edge. This means that latency is at least
> > > as good as 1/57,000 sec = 0.013 microseconds.
> > 
> > Assuming you mean 75,000 then ... 
> > Thats 0.013 MILLISECONDS which is 13 microseconds and its not likely.
> 
> Yes 13 microseconds.
> 
> > I bet that your data source drops data or looks at some handshake
> > pins on the parallel connect.
> > 
> 
> No. You can easily read into memory 75,000 bytes per second from the
> parallel port, hell RS-232C will do 22,400++ bytes per second (224,000
> baud) on a Windows machine, done all the while to feed a PROM burner. I
> never measured Linux RS-232C, but it's got to be at least as good.

There's >16bytes FIFO at the rs-232, and kernel uses flip buffers so
that it does nlot have to wake userspace each time.

-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  parent reply	other threads:[~2002-08-28 21:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-27  9:58 interrupt latency 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
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 [this message]
2002-08-27 18:05 ` Dag Nygren
  -- strict thread matches above, loose matches on Subject: below --
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=20020828124204.B39@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Siegfried.Wessler@de.hbm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    --cc=root@chaos.analogic.com \
    --cc=yodaiken@fsmlabs.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