From: Thomas Gleixner <tglx@linutronix.de>
To: Jaswinder Singh <jaswinderlinuxrt@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.23-rc9-rt2
Date: Mon, 8 Oct 2007 17:07:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.0.9999.0710081644230.25146@localhost.localdomain> (raw)
In-Reply-To: <1985e0f60710080734y4897a8e1ke253b6d4273146ec@mail.gmail.com>
On Mon, 8 Oct 2007, Jaswinder Singh wrote:
> On 10/8/07, Steven Rostedt <rostedt@goodmis.org> wrote:
> >
> > Not sure what you mean by this, since interrupt handlers are run as
> > threads and are fully preemptible.
> >
> I think by nested or reentrant interrupt handling technique you can
> further reduce latencies.
> what you think.
Interrupt handlers in vanilla Linux and preempt-rt are never reentrant.
There is no advantage of allowing interrupt handler reentrancy, quite the
contrary it makes the code more complex.
The interrupt handlers in preempt-rt are running in threads. One thread
per interrupt, so depending on the thread priority the handlers a handler
of one interrupt can preempt the running handler of another interrupt.
> Can we can get guaranteed realtime throughput by using these realtime patch.
Realtime is not about throughput. It's about determinism.
tglx
prev parent reply other threads:[~2007-10-08 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 22:20 2.6.23-rc9-rt2 Steven Rostedt
2007-10-07 13:35 ` 2.6.23-rc9-rt2 Jaswinder Singh
2007-10-08 13:52 ` 2.6.23-rc9-rt2 Steven Rostedt
2007-10-08 14:34 ` 2.6.23-rc9-rt2 Jaswinder Singh
2007-10-08 15:07 ` Thomas Gleixner [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=alpine.LFD.0.9999.0710081644230.25146@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=jaswinderlinuxrt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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