linux-kernel - Re: 2.6.23-rc9-rt2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LFD.0.9999.0710081644230.25146@localhost.localdomain>
Date:	Mon, 8 Oct 2007 17:07:34 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jaswinder Singh <jaswinderlinuxrt@...il.com>
cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.23-rc9-rt2

On Mon, 8 Oct 2007, Jaswinder Singh wrote:
> On 10/8/07, Steven Rostedt <rostedt@...dmis.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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/