From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Josh Boyer <jwboyer@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: 3.0-git15 Atomic scheduling in pidmap_init
Date: Wed, 24 Aug 2011 16:57:02 -0700 [thread overview]
Message-ID: <20110824235702.GC2417@linux.vnet.ibm.com> (raw)
In-Reply-To: <20110824233422.GD26417@somewhere.redhat.com>
On Thu, Aug 25, 2011 at 01:34:24AM +0200, Frederic Weisbecker wrote:
> On Wed, Aug 24, 2011 at 04:12:55PM -0700, Paul E. McKenney wrote:
> > Indeed, this was a bogus patch. The version I posted on the -rcu git
> > tree a few days ago has the correct "rdp->qs_pending = 0". I thought
> > that I had chased down all the bogus copies, but obviously not. :-(
>
> Ah ok.
>
> > > Should it perhaps set it to 1 only if we have rnp->gpnum > rnp->completed ?
> >
> > I would rather keep it simple. If rnp->gpnum > rnp->completed, then
> > the newly onlined CPU will notice and adjust appropriately soon enough.
>
> Ah, just to ensure I understood well is that because rcu_pending() (called
> from tick) would detect rnp->gpnum != rdp->gpnum and thus trigger the softirq
> that notes the new gpnum and toggles qs_pending?
Yep, that is the theory, anyway. ;-)
Thanx, Paul
> > > > rdp->passed_quiesc_completed = rnp->completed - 1;
> > > > }
> > > > raw_spin_unlock(&rnp->lock); /* irqs already disabled. */
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2011-08-24 23:57 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 15:46 3.0-git15 Atomic scheduling in pidmap_init Josh Boyer
2011-08-04 11:46 ` Josh Boyer
2011-08-04 14:04 ` Paul E. McKenney
2011-08-04 15:06 ` Josh Boyer
2011-08-04 16:26 ` Paul E. McKenney
2011-08-04 17:31 ` Josh Boyer
2011-08-05 1:19 ` Josh Boyer
2011-08-05 6:56 ` Paul E. McKenney
2011-08-05 14:22 ` Josh Boyer
2011-08-05 17:08 ` Frederic Weisbecker
2011-08-05 22:26 ` Paul E. McKenney
2011-08-05 23:12 ` Frederic Weisbecker
2011-08-08 2:09 ` Paul E. McKenney
2011-08-08 2:55 ` Frederic Weisbecker
2011-08-08 3:10 ` Paul E. McKenney
2011-08-09 11:35 ` Frederic Weisbecker
2011-08-10 12:45 ` Josh Boyer
2011-08-10 14:53 ` Frederic Weisbecker
2011-08-10 15:03 ` Josh Boyer
2011-08-14 23:04 ` Paul E. McKenney
2011-08-15 14:04 ` Josh Boyer
2011-08-15 15:20 ` Paul E. McKenney
2011-08-17 22:37 ` Josh Boyer
2011-08-17 22:49 ` Paul E. McKenney
2011-08-17 23:02 ` Josh Boyer
2011-08-17 23:06 ` Frederic Weisbecker
2011-08-17 23:17 ` Josh Boyer
2011-08-18 18:35 ` Paul E. McKenney
2011-08-18 19:11 ` Josh Boyer
2011-08-18 21:00 ` Andrew Morton
2011-08-18 21:23 ` Paul E. McKenney
2011-08-18 21:55 ` Paul E. McKenney
2011-08-18 22:21 ` Josh Boyer
2011-08-18 23:01 ` Paul E. McKenney
2011-08-24 22:45 ` Frederic Weisbecker
2011-08-24 23:12 ` Paul E. McKenney
2011-08-24 23:34 ` Frederic Weisbecker
2011-08-24 23:57 ` Paul E. McKenney [this message]
2011-08-18 22:19 ` Josh Boyer
2011-08-18 23:16 ` Paul E. McKenney
2011-08-18 23:27 ` Andrew Morton
2011-08-19 0:38 ` 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=20110824235702.GC2417@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.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