From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755524AbaEJMbX (ORCPT ); Sat, 10 May 2014 08:31:23 -0400 Received: from www.linutronix.de ([62.245.132.108]:40960 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753728AbaEJMbV (ORCPT ); Sat, 10 May 2014 08:31:21 -0400 Date: Sat, 10 May 2014 14:31:28 +0200 (CEST) From: Thomas Gleixner To: Frederic Weisbecker cc: "Paul E. McKenney" , Christoph Lameter , Andrew Morton , Gilad Ben-Yossef , Tejun Heo , Mike Frysinger , Minchan Kim , Hakan Akkan , Max Krasnyansky , LKML , linux-mm@kvack.org, hughd@google.com, viresh.kumar@linaro.org, Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , John Stultz Subject: Re: vmstat: On demand vmstat workers V4 In-Reply-To: <20140510004843.GB32393@localhost.localdomain> Message-ID: References: <20140508142903.c2ef166c95d2b8acd0d7ea7d@linux-foundation.org> <20140509234745.GB8754@linux.vnet.ibm.com> <20140510004843.GB32393@localhost.localdomain> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 10 May 2014, Frederic Weisbecker wrote: > But I still have the plan to make the timekeeper use the full sysidle > facility in order to adaptively get to dynticks idle. > > Reminder for others: in NO_HZ_FULL, the timekeeper (always CPU 0) stays > completely periodic. It can't enter in dynticks idle mode because it > must maintain timekeeping on behalf of full dynticks CPUs. So that's > a power issue. > > But Paul has a feature in RCU that lets us know when all CPUs are idle > and the timekeeper can finally sleep. Then when a full nohz CPU wakes > up from idle, it sends an IPI to the timekeeper if needed so the latter > restarts timekeeping maintainance. > > It's not complicated to add to the timer code. > Most of the code is already there, in RCU, for a while already. > > Are we keeping that direction? So the idea is that the timekeeper stays on cpu0, but if everything is idle it is allowed to take a long nap as well. So if some other cpu wakes up it updates timekeeping without taking over the time keeper duty and if it has work to do, it kicks cpu0 into gear. If it just goes back to sleep, then nothing to do. No objections from my side. Thanks, tglx