From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
josh@joshtriplett.org, dvhltc@us.ibm.com, niv@us.ibm.com,
tglx@linutronix.de, rostedt@goodmis.org, Valdis.Kletnieks@vt.edu,
dhowells@redhat.com
Subject: Re: [PATCH tip/core/rcu 0/4] Josh and Ingo review feedback and bloatwatch RCU
Date: Wed, 23 Sep 2009 06:21:37 -0700 [thread overview]
Message-ID: <20090923132137.GE6845@linux.vnet.ibm.com> (raw)
In-Reply-To: <1253688342.7695.99.camel@twins>
On Wed, Sep 23, 2009 at 08:45:42AM +0200, Peter Zijlstra wrote:
> On Tue, 2009-09-22 at 15:24 -0700, Paul E. McKenney wrote:
> > This patch set applies two sets of review feedback from Josh Triplett and
> > checkpatch feedback from Ingo Molnar. It also contains a forward-port
> > of Bloatwatch RCU, courtesy of David Howells.
>
> It would be much easier to review if these patches had a changelog
> describing the problem they address :-)
>
> The first one seems to do:
>
> A)
> - aggregate 'rsp->completed == rsp->gpnum' expressions into a
> common function.
>
> - consistently use ACCESS_ONCE() in the above mentioned function
>
> B)
> - use DIV_ROUND_UP()
>
> C)
> - aggregate list_empty(&rnp->blocked_tasks[rnp->gpnum & 0x01])
> expressions into a common function.
>
>
> Could have been three patches, but ACK.
Good point, I will re-submit with the changelog and your Acked-by.
> The second patch seems to mostly add comments, but also moves code
> around and makes it static, which could have been split in two patches.
>
> The purpose of the move code around bit could be a cleanup?
Yep. The main point was that the old way had a bunch of random
forward declarations, while the new way has the plugins themselves
forward-declared, which (to me at least) makes a lot more sense.
> Looks to preserve the logic, but didn't go out on a limb to verify, ACK.
Again, will re-submit with your acked-by.
> The third and fourth do have an adequate changelog :-)
;-)
Thank you for looking this over!!!
Thanx, Paul
next prev parent reply other threads:[~2009-09-23 13:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 22:24 [PATCH tip/core/rcu 0/4] Josh and Ingo review feedback and bloatwatch RCU Paul E. McKenney
2009-09-22 22:25 ` [PATCH tip/core/rcu 1/4] Apply review feedback from Josh Triplett, part 1 Paul E. McKenney
2009-09-22 22:25 ` [PATCH tip/core/rcu 2/4] Apply review feedback from Josh Triplett, part 2 Paul E. McKenney
2009-09-22 22:25 ` [PATCH tip/core/rcu 3/4] Apply Ingo's checkpatch feedback Paul E. McKenney
2009-09-22 22:25 ` [PATCH tip/core/rcu 4/4] v6 RCU: the bloatwatch edition Paul E. McKenney
2009-09-23 6:45 ` [PATCH tip/core/rcu 0/4] Josh and Ingo review feedback and bloatwatch RCU Peter Zijlstra
2009-09-23 13:21 ` Paul E. McKenney [this message]
2009-09-23 19:04 ` Josh Triplett
-- strict thread matches above, loose matches on Subject: below --
2009-09-23 16:50 [PATCH tip/core/rcu 0/4] Josh and Ingo review feedback and Bloatwatch RCU Paul E. McKenney
2009-09-23 19:10 ` Josh Triplett
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=20090923132137.GE6845@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=dvhltc@us.ibm.com \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=niv@us.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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