[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110502082711.GW2297@linux.vnet.ibm.com>
Date: Mon, 2 May 2011 01:27:11 -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 11/86] rcu: Add boosting to
TREE_PREEMPT_RCU tracing
On Sun, May 01, 2011 at 08:52:25AM -0700, Josh Triplett wrote:
> On Sun, May 01, 2011 at 06:20:51AM -0700, Paul E. McKenney wrote:
> > From: Paul E. McKenney <paul.mckenney@...aro.org>
> >
> > Includes total number of tasks boosted, number boosted on behalf of each
> > of normal and expedited grace periods, and statistics on attempts to
> > initiate boosting that failed for various reasons.
>
> In this patch series, you have several cases where you improve the trace
> output in one patch, and then update the documentation in a subsequent
> patch. You might consider doing both in the same patch, so that at each
> step the documentation matches the kernel.
The reason I do the documentation second is that it allows me to copy
the exact output from a test run, which has the nice side-effect of
making sure that I really am getting the documentation correct. Or at
least of reducing the probability of getting it wrong... ;-)
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