From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Tim Sander <tim01@vlsi.informatik.tu-darmstadt.de>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
peterz@infradead.org, rostedt@goodmis.org,
Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
edumazet@google.com, darren@dvhart.com, fweisbec@gmail.com,
sbw@mit.edu, patches@linaro.org
Subject: Re: Does anyone use CONFIG_TINY_PREEMPT_RCU?
Date: Tue, 13 Nov 2012 13:20:34 -0800 [thread overview]
Message-ID: <20121113212034.GD2489@linux.vnet.ibm.com> (raw)
In-Reply-To: <201211132122.30259.tim01@vlsi.informatik.tu-darmstadt.de>
On Tue, Nov 13, 2012 at 09:22:29PM +0100, Tim Sander wrote:
> Hi Paul
> > I know of people using TINY_RCU, TREE_RCU, and TREE_PREEMPT_RCU, but I
> > have not heard of anyone using TINY_PREEMPT_RCU for whom TREE_PREEMPT_RCU
> > was not a viable option (in contrast, the people running Linux on
> > tiny-memmory systems typically use TINY_RCU). Of course, if no one
> > really needs it, the proper thing to do is to remove it.
> >
> > So, if you need TINY_PREEMPT_RCU, please let me know. Otherwise, I will
> > remove it, probably in the 3.9 timeframe.
> I am using TINY_PREEMPT_RCU on the i.mx35 platform. I am currently on 3.4-rt
> since the 3.6 compile failed due to for my config? Some strange device tree
> stuff which i haven't had the time to figure out why.
OK, how much memory does your device have?
Thanx, Paul
next prev parent reply other threads:[~2012-11-13 21:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-13 0:49 Does anyone use CONFIG_TINY_PREEMPT_RCU? Paul E. McKenney
2012-11-13 1:12 ` Frederic Weisbecker
2012-11-13 1:17 ` Josh Triplett
2012-11-13 1:34 ` Frederic Weisbecker
2012-11-13 1:42 ` Paul E. McKenney
2012-11-13 1:32 ` Paul E. McKenney
2012-11-13 14:46 ` Nick Bowler
2012-11-13 17:08 ` Paul E. McKenney
2012-11-13 17:56 ` Nick Bowler
2012-11-13 21:19 ` Paul E. McKenney
2012-11-13 21:47 ` Nick Bowler
2012-11-13 22:25 ` Paul E. McKenney
2012-11-13 22:40 ` Nick Bowler
2012-11-14 0:05 ` Paul E. McKenney
[not found] ` <CAGChsmOBB1yFNP5xSa06v+CYn0A=AjcZTyAzL8npWRdNYYLBZA@mail.gmail.com>
2012-11-13 23:04 ` Paul E. McKenney
2012-11-13 20:22 ` Tim Sander
2012-11-13 21:20 ` Paul E. McKenney [this message]
2012-11-13 23:32 ` Tim Sander
2012-11-14 0:06 ` Paul E. McKenney
2012-11-14 0:36 ` Josh Triplett
2012-11-14 1:07 ` Paul E. McKenney
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=20121113212034.GD2489@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=patches@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sbw@mit.edu \
--cc=tglx@linutronix.de \
--cc=tim01@vlsi.informatik.tu-darmstadt.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).