public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
	linux-kernel@vger.kernel.org,
	Dipankar Sarma <dipankar@in.ibm.com>,
	Manfred Spraul <manfred@colorfullife.com>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 4/5] rcu: join rcu_ctrlblk and rcu_state
Date: Mon, 9 Jan 2006 18:54:39 -0800	[thread overview]
Message-ID: <20060110025439.GI14738@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0601091641000.5588@g5.osdl.org>

On Mon, Jan 09, 2006 at 04:43:17PM -0800, Linus Torvalds wrote:
> 
> On Mon, 9 Jan 2006, Paul E. McKenney wrote:
> > 
> > This patch looks sane to me.  It passes a short one-hour rcutorture
> > on ppc64 and x86, firing up some overnight runs as well.
> > 
> > Dipankar, Manfred, any other concerns?  Cacheline alignment?  (Seems
> > to me this code is far enough from the fastpath that this should not
> > be a problem, but thought I should ask.)
> 
> I'd ask you and Oleg to re-synchronize, and perhaps Oleg to re-send the 
> (part of?) the series that has no debate. I'm unsure, for example, whether 
> #2 was just to be dropped.

I believe that the original #2 is to be dropped, but that the patch Oleg
submitted in:

	http://marc.theaimsgroup.com/?l=linux-kernel&m=113681388600342&w=2

may be needed.  I have added Vatsa to the CC to get his take on this.

However, this patch should be independent from #4, so it should be OK
to apply an updated #4 first while we are working out what to do about #2.

> I already applied #1, and it looks like there's agreement on #3 and #4, 
> but basically, just to make sure, can Oleg please re-send to make sure I 
> got it right?
> 
> Getting a screwed-up RCU thing is going to be too painful to debug, so I'd 
> rather get it right the first time it hits my tree..

Been there more times than I care to admit, and I most definitely agree!!!

							Thanx, Paul

  reply	other threads:[~2006-01-10  2:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-08 19:19 [PATCH 4/5] rcu: join rcu_ctrlblk and rcu_state Oleg Nesterov
2006-01-10  0:28 ` Paul E. McKenney
2006-01-10  0:43   ` Linus Torvalds
2006-01-10  2:54     ` Paul E. McKenney [this message]
2006-01-10 10:02       ` Srivatsa Vaddagiri
2006-01-10 18:09   ` Dipankar Sarma
2006-01-10 20:44     ` Manfred Spraul
2006-01-10 21:51       ` 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=20060110025439.GI14738@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=dipankar@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=oleg@tv-sign.ru \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox