Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759486AbaGSAoo (ORCPT ); Fri, 18 Jul 2014 20:44:44 -0400 Received: from mail-wg0-f48.google.com ([74.125.82.48]:42751 "EHLO mail-wg0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751530AbaGSAob (ORCPT ); Fri, 18 Jul 2014 20:44:31 -0400 From: Frederic Weisbecker To: LKML Cc: Frederic Weisbecker , Ingo Molnar , "Paul E. McKenney" , Peter Zijlstra , Steven Rostedt , Thomas Gleixner , Viresh Kumar Subject: [PATCH 02/10] nohz: Kick full dynticks timer targets with an empty IPI Date: Sat, 19 Jul 2014 02:44:13 +0200 Message-Id: <1405730661-9355-3-git-send-email-fweisbec@gmail.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1405730661-9355-1-git-send-email-fweisbec@gmail.com> References: <1405730661-9355-1-git-send-email-fweisbec@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org While we enqueue a new timer on a dynticks target, we must send it an IPI so that it reschedules the next tick accordingly. Now all we need for that is to run irq_exit() on the target. Hence an empty IRQ is way enough. We don't need to run tick_nohz_full_check() and all the overhead that comes with the several cmpxchg() necessary for irq work list and state progress. So lets use a void irq work instead. Cc: Ingo Molnar Cc: Paul E. McKenney Cc: Peter Zijlstra Cc: Steven Rostedt Cc: Thomas Gleixner Cc: Viresh Kumar Signed-off-by: Frederic Weisbecker --- kernel/sched/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index 7f3063c..f3e48b8 100644 --- a/kernel/sched/core.c +++ b/kernel/sched/core.c @@ -693,7 +693,7 @@ static bool wake_up_full_nohz_cpu(int cpu) if (tick_nohz_full_cpu(cpu)) { if (cpu != smp_processor_id() || tick_nohz_tick_stopped()) - tick_nohz_full_kick_cpu(cpu); + irq_work_void_on(cpu); return true; } -- 1.8.3.1 -- 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/