public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Kuhn <bkuhn@metrowerks.com>
To: Martin Schlemmer <azarah@nosferatu.za.org>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: [announcement, patch] real-time interrupts for the Linux kernel
Date: Sun, 11 Jan 2004 17:48:58 +0100	[thread overview]
Message-ID: <40017E7A.4070500@metrowerks.com> (raw)
In-Reply-To: 1073827448.9096.119.camel@nosferatu.lan

Martin Schlemmer wrote:

> Do you have actual benchmarks,

The example kernel module and application are doing
some simple benchmarking: the local APIC timer
runs in period mode (1 kHz), and the interrupt
handler then reads out the current value of the timer.
Then you know how long it took from the occurence of the
interrupt to the moment the handler has been invoked
(including context switching, do_IRQ and handle_IRQ_event).

Number is my setup under heavy load (ping-flood, glxgears):

                     99.9%     worst case
high priority        3.1 µs       5.2 µs
standard kernel    486.1 µs     500.8 µs

"99.9%" means that 99.9% of the interrupts or handled
in withing the given time.


> and what 2.4 rather than 2.6 ?

I started with 2.4 becuase that's the devil i know, but from
what i have inspected so far, adopting this scheme for 2.6
should be doable within a day - i just started to work in it.

best regards

Bernhard


      reply	other threads:[~2004-01-11 16:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09  1:44 [announcement, patch] real-time interrupts for the Linux kernel Bernhard Kuhn
2004-01-11  0:02 ` Bill Huey
2004-01-11  9:14 ` Voicu Liviu
2004-01-11 16:38   ` Bernhard Kuhn
2004-01-11 19:35     ` Voicu Liviu
2004-01-11 13:24 ` Martin Schlemmer
2004-01-11 16:48   ` Bernhard Kuhn [this message]

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=40017E7A.4070500@metrowerks.com \
    --to=bkuhn@metrowerks.com \
    --cc=azarah@nosferatu.za.org \
    --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