From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>,
laijs@cn.fujitsu.com, dipankar@in.ibm.com,
"Andrew Morton" <akpm@linux-foundation.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@polymtl.ca>,
josh@joshtriplett.org, niv@us.ibm.com,
"Thomas Gleixner" <tglx@linutronix.de>,
"Peter Zijlstra" <peterz@infradead.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"David Howells" <dhowells@redhat.com>,
edumazet@google.com, darren@dvhart.com,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Silas Boyd-Wickizer" <sbw@mit.edu>,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH tip/core/rcu 8/9] nohz_full: Add full-system-idle state machine
Date: Sat, 7 Sep 2013 11:59:42 -0700 [thread overview]
Message-ID: <20130907185942.GG3966@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAMuHMdXsAfo=LMF8E84_Lyhs+w5c3VKCEe7ZW5Bs7fwFV+J==w@mail.gmail.com>
On Sat, Sep 07, 2013 at 01:22:57PM +0200, Geert Uytterhoeven wrote:
> On Fri, Sep 6, 2013 at 8:50 PM, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Fri, Sep 6, 2013 at 7:30 PM, Paul E. McKenney
> > <paulmck@linux.vnet.ibm.com> wrote:
> >>> Furthermore, it seems only hexagon, metag, mips, and x86 set NR_CPUS to 1
> >>> if !SMP. On other architectures, NR_CPUS is not defined and presumed to be 0.
> >>
> >> Would it make sense to require that NR_CPUS=1 for !SMP?
> >
> > Yes, this looks reasonable to me.
>
> Perhaps we can invert the logic and define only NR_CPUS in arch-specific
> code, and derive SMP from NR_CPUS != 1 in generic code?
If we always had NR_CPUS defined, that might be a good way to go.
We would of course need acks from the various arch maintainers. I am
guessing that we are OK for m68k. ;-)
Thanx, Paul
next prev parent reply other threads:[~2013-09-07 18:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130820024700.GA31075@linux.vnet.ibm.com>
[not found] ` <1376966841-31774-1-git-send-email-paulmck@linux.vnet.ibm.com>
[not found] ` <1376966841-31774-8-git-send-email-paulmck@linux.vnet.ibm.com>
2013-09-06 8:08 ` [PATCH tip/core/rcu 8/9] nohz_full: Add full-system-idle state machine Geert Uytterhoeven
2013-09-06 8:08 ` Geert Uytterhoeven
2013-09-06 17:30 ` Paul E. McKenney
2013-09-06 17:30 ` Paul E. McKenney
2013-09-06 18:50 ` Geert Uytterhoeven
2013-09-06 19:32 ` Paul E. McKenney
2013-09-06 19:32 ` Paul E. McKenney
2013-09-07 11:22 ` Geert Uytterhoeven
2013-09-07 18:59 ` Paul E. McKenney [this message]
2013-09-07 18:59 ` Paul E. McKenney
2013-09-07 9:13 ` Yann E. MORIN
2013-09-07 18:57 ` Paul E. McKenney
2013-09-07 18:57 ` Paul E. McKenney
2013-09-08 10:32 ` Yann E. MORIN
2013-09-08 10:32 ` Yann E. MORIN
2013-09-08 10:46 ` Frederic Weisbecker
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=20130907185942.GG3966@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=darren@dvhart.com \
--cc=dhowells@redhat.com \
--cc=dipankar@in.ibm.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=geert@linux-m68k.org \
--cc=josh@joshtriplett.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--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=sbw@mit.edu \
--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;
as well as URLs for NNTP newsgroup(s).