From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: "Paul E. McKenney" <pmckenne@us.ibm.com>
Cc: Bill Huey <bhuey@lnxw.com>, linux-kernel@vger.kernel.org
Subject: NMI reentrant RCU list for -rt kernels
Date: Sat, 22 Jul 2006 11:29:34 -0400 [thread overview]
Message-ID: <20060722152933.GA17148@Krystal> (raw)
Hi Paul,
Following your presentation on RCU lists for -rt kernel, discussing with Bill
Huey led me to the following idea that could solve the problem of NMI reentrancy
of RCU read side in the -rt kernels.
If we consider that the RCU list modification that makes the read side
lock preemptible is only needed for very long code paths, we could leave the
original RCU implementation along with the preemptible one, so that very short
and frequent code paths could benefit of using the very cheap preempt count
protection without having a too big impact on the scheduler latency.
For instance, my LTTng tracer disables the preemption for about 95 ns, which I
doubt would be a problem for real-time behavior. I could easily fix maximum
a maximum list size so it can be run in a constant time.
So, basically, the idea is to have two RCU API that could take names like :
atomic_rcu_* and rcu_*
Does this idea make sense ?
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2006-07-22 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-22 15:29 Mathieu Desnoyers [this message]
2006-07-22 18:14 ` NMI reentrant RCU list for -rt kernels Esben Nielsen
2006-07-24 17:24 ` Bill Huey
2006-07-24 17:35 ` Bill Huey
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=20060722152933.GA17148@Krystal \
--to=compudj@krystal.dyndns.org \
--cc=bhuey@lnxw.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pmckenne@us.ibm.com \
/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).