From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH v3 02/22] kthread/smpboot: Do not park in kthread_create_on_cpu() Date: Wed, 25 Nov 2015 22:16:16 +0100 (CET) Message-ID: References: <1447853127-3461-1-git-send-email-pmladek@suse.com> <1447853127-3461-3-git-send-email-pmladek@suse.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: <1447853127-3461-3-git-send-email-pmladek-IBi9RG/b67k@public.gmane.org> Sender: linux-api-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Petr Mladek Cc: Andrew Morton , Oleg Nesterov , Tejun Heo , Ingo Molnar , Peter Zijlstra , Steven Rostedt , "Paul E. McKenney" , Josh Triplett , Linus Torvalds , Jiri Kosina , Borislav Petkov , Michal Hocko , linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, Vlastimil Babka , linux-api-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-api@vger.kernel.org On Wed, 18 Nov 2015, Petr Mladek wrote: > kthread_create_on_cpu() was added by the commit 2a1d446019f9a5983e > ("kthread: Implement park/unpark facility"). It is currently used > only when enabling new CPU. For this purpose, the newly created > kthread has to be parked. > > The CPU binding is a bit tricky. The kthread is parked when the CPU > has not been allowed yet. And the CPU is bound when the kthread > is unparked. > > The function would be useful for more per-CPU kthreads, e.g. > bnx2fc_thread, fcoethread. For this purpose, the newly created > kthread should stay in the uninterruptible state. > > This patch moves the parking into smpboot. It binds the thread > already when created. Then the function might be used universally. > Also the behavior is consistent with kthread_create() and > kthread_create_on_node(). > > Signed-off-by: Petr Mladek Reviewed-by: Thomas Gleixner