All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] RCU changes for v3.4
Date: Mon, 19 Mar 2012 20:33:00 -0700	[thread overview]
Message-ID: <20120320033300.GH2393@linux.vnet.ibm.com> (raw)
In-Reply-To: <CA+55aFyezw6yW2g6hOAOeZ5vRm0xUNPQyD4eo0wRHMHiN3Z+kQ@mail.gmail.com>

On Mon, Mar 19, 2012 at 05:18:21PM -0700, Linus Torvalds wrote:
> On Mon, Mar 19, 2012 at 8:23 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please pull the latest core-rcu-for-linus git tree from:
> >
> >   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-rcu-for-linus
> 
> So Ingo, Paul - I'd really have liked to have some high-level
> user-readable explanation of the changes that I could have put in the
> merge message.
> 
> This is especially true for something like RCU, which (a) seems to be
> continually growing and (b) has had cases of "oops, now it stopped
> working" or "uhhuh, new rules due to new rcu implementations
> interacting differently with spinlocks" etc.
> 
> So when the diffstat summary looks like this:
> 
>   29 files changed, 2965 insertions(+), 642 deletions(-)
> 
> with basically 2000+ new lines (yes, many of them in Documebntation,
> happily, but rcutree grew noticeably too), it really would have been
> nice to have some blurb about what the heck actually happened, ok?

Yep, 2072 of the net additions were in Documentation.

> I'm starting to get explanations in signed tags or in the "please
> pull" messages from a fairly large number of maintainers now, and the
> pulls from Ingo are beginning to look sad and unexplained in contrast.

Many of the change to rcutree.c were due to additions of checks for illegal
use of RCU from idle or offlined CPUs, reworking of the CPU-offline code
path, and fixes to allow use of RCU from idle CPUs (which has always been
illegal, but many uses have nevertheless slipped in over the years).

If it would help, I would be happy to put together an itemized list.
I will of course do so for the next merge window.

							Thanx, Paul


  reply	other threads:[~2012-03-20  3:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 15:23 [GIT PULL] RCU changes for v3.4 Ingo Molnar
2012-03-20  0:18 ` Linus Torvalds
2012-03-20  3:33   ` Paul E. McKenney [this message]
2012-03-20  6:13     ` Ingo Molnar
2012-03-23  1:08     ` Linus Torvalds
2012-03-23 19:21       ` Paul E. McKenney
2012-03-23 19:39         ` Linus Torvalds
2012-03-23 21:16           ` Paul E. McKenney
2012-03-23 21:25             ` Paul E. McKenney
2012-03-24  1:47               ` Paul E. McKenney
2012-03-24  2:00                 ` Linus Torvalds
2012-03-24  4:17                   ` Paul E. McKenney
2012-03-24  4:25                     ` Linus Torvalds
2012-03-24  4:48                       ` 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=20120320033300.GH2393@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.