[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1154116918.13509.162.camel@localhost.localdomain>
Date: Fri, 28 Jul 2006 21:01:58 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Theodore Tso <tytso@....edu>, Neil Horman <nhorman@...driver.com>,
"H. Peter Anvin" <hpa@...or.com>,
Segher Boessenkool <segher@...nel.crashing.org>,
Dave Airlie <airlied@...il.com>, linux-kernel@...r.kernel.org,
a.zummo@...ertech.it, jg@...edesktop.org
Subject: Re: A better interface, perhaps: a timed signal flag
Ar Gwe, 2006-07-28 am 12:44 -0400, ysgrifennodd Steven Rostedt:
> But for real-time applications, the signal handling has a huge latency.
For real-time you want a thread. Our thread switching is extremely fast
and threads unlike signals can have RT priorities of their own
-
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/
Powered by blists - more mailing lists