From: Steven Rostedt <rostedt@goodmis.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
RT <linux-rt-users@vger.kernel.org>
Subject: Using random in interrupts for RT
Date: Tue, 14 Aug 2012 10:30:49 -0400 [thread overview]
Message-ID: <1344954649.6724.13.camel@gandalf.stny.rr.com> (raw)
Thomas,
Ben Hutchings asked me if we still need "genirq: Disable random call on
preempt-rt" for -rt? With commit 902c098a366 "random: use lockless
techniques in the interrupt path" there is no more locks used. But does
it still produce high latencies?
-- Steve
next reply other threads:[~2012-08-14 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 14:30 Steven Rostedt [this message]
2012-08-14 15:17 ` Using random in interrupts for RT Thomas Gleixner
2012-08-21 18:12 ` Steven Rostedt
2012-08-21 19:12 ` Ben Hutchings
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=1344954649.6724.13.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).