From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Rusty Russell <rusty@rustcorp.com.au>, Tejun Heo <tj@kernel.org>
Subject: Re: [RFC patch V2 0/7] Per cpu thread hotplug infrastructure
Date: Tue, 26 Jun 2012 16:26:20 -0700 [thread overview]
Message-ID: <20120626232620.GA24468@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120615140217.933711648@linutronix.de>
On Fri, Jun 15, 2012 at 02:13:19PM -0000, Thomas Gleixner wrote:
> The following series implements the infrastructure for parking and
> unparking kernel threads to avoid the full teardown and fork on cpu
> hotplug operations along with management infrastructure for hotplug
> and users.
>
> Changes since V1:
>
> - Addressed the review comments
> - Fixed a missing state update in parkme (reported by Paul)
> - Simplified rcu_yield()
> - Added Pauls RCU conversion
>
> Full diffstat below. Due to the RCU cleanup we now remove more code
> than we add. :)
;-)
With the exception of a build error for CONFIG_SMP=y:
Tested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
I finally tracked down a hang, which turned out to be an unrelated bug
of mine that happened to be triggered more reliably with these patches
applied, hence the delay. Sigh!
For CONFIG_SMP=y:
softirq.c:(.text+0xa6d3): undefined reference to `smpboot_thread_check_parking'
softirq.c:(.init.text+0x4aa): undefined reference to `smpboot_register_percpu_thread'
softirq.c:(.text+0xb763): undefined reference to `smpboot_thread_check_parking'
softirq.c:(.init.text+0x48e): undefined reference to `smpboot_register_percpu_thread'
My approach would be to make smpboot.o be unconditionally created by
kernel/Makefile and to use conditional compilation as needed. The real
question is whether we want to allow parking in !SMP kernels. I cannot
see why we wouldn't -- there might be other reasons to park besides
CPU hotplug. Thoughts?
Thanx, Paul
> Thanks,
>
> tglx
> ---
> drivers/infiniband/hw/ehca/ehca_irq.c | 240 ++++++++-------------
> drivers/infiniband/hw/ehca/ehca_irq.h | 5
> include/linux/kthread.h | 11
> include/linux/smpboot.h | 40 +++
> kernel/cpu.c | 10
> kernel/kthread.c | 184 ++++++++++++++--
> kernel/rcutree.c | 12 -
> kernel/rcutree.h | 15 -
> kernel/rcutree_plugin.h | 375 +++++-----------------------------
> kernel/rcutree_trace.c | 3
> kernel/smpboot.c | 206 ++++++++++++++++++
> kernel/smpboot.h | 4
> kernel/softirq.c | 84 +------
> kernel/watchdog.c | 232 ++++++---------------
> 14 files changed, 678 insertions(+), 743 deletions(-)
>
next prev parent reply other threads:[~2012-06-26 23:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 14:13 [RFC patch V2 0/7] Per cpu thread hotplug infrastructure Thomas Gleixner
2012-06-15 14:13 ` [RFC patch V2 1/7] rcu: Yield simpler Thomas Gleixner
2012-06-15 14:13 ` [RFC patch V2 2/7] kthread: Implement park/unpark facility Thomas Gleixner
2012-06-18 8:43 ` Namhyung Kim
2012-06-18 8:50 ` Thomas Gleixner
2012-06-15 14:13 ` [RFC patch V2 3/7] smpboot: Provide infrastructure for percpu hotplug threads Thomas Gleixner
2012-06-15 14:13 ` [RFC patch V2 4/7] softirq: Use hotplug thread infrastructure Thomas Gleixner
2012-06-15 21:49 ` Paul E. McKenney
2012-06-15 14:13 ` [RFC patch V2 6/7] rcu: Use smp_hotplug_thread facility for RCUs per-CPU kthread Thomas Gleixner
2012-06-15 14:13 ` [RFC patch V2 5/7] watchdog: Use hotplug thread infrastructure Thomas Gleixner
2012-06-15 14:13 ` [RFC patch V2 7/7] infiniband: ehca: " Thomas Gleixner
2012-06-26 23:26 ` Paul E. McKenney [this message]
2012-06-27 9:52 ` [RFC patch V2 0/7] Per cpu thread hotplug infrastructure Peter Zijlstra
2012-06-27 14:14 ` 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=20120626232620.GA24468@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=tj@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