[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110502221919.GJ2294@linux.vnet.ibm.com>
Date: Mon, 2 May 2011 15:19:19 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
patches@...aro.org, "Paul E. McKenney" <paul.mckenney@...aro.org>
Subject: Re: [PATCH tip/core/rcu 17/86] rcu: fix boost-tracing bug and
update tracing documentation
On Mon, May 02, 2011 at 10:44:42AM -0700, Josh Triplett wrote:
> On Mon, May 02, 2011 at 01:33:01AM -0700, Paul E. McKenney wrote:
> > On Sun, May 01, 2011 at 08:43:10AM -0700, Josh Triplett wrote:
> > > Also, does rcu/rcutorture appear with rcutorture not loaded? Hopefully
> > > not, since rcutorture shouldn't take up any additional resources when
> > > not loaded.
> >
> > Not much choice, unfortunately. If I put the info into rcutorture, then
> > I lose it when rcutorture is unloaded. This is problematic in automated
> > tests that repeatedly load and unload rcutorture.
> >
> > But the amount of data is small, and I set things up so that TINY_RCU
> > can omit this. TREE_RCU is big enough that it doesn't really matter.
>
> You could omit it entirely if CONFIG_RCU_TORTURE_TEST=n (rather than
> =m).
I could, but it doesn't seem worth it. Of course, it might be just
the fact that I am writing this from the Toronto airport...
Thanx, Paul
--
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