From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753307Ab1H3WoN (ORCPT ); Tue, 30 Aug 2011 18:44:13 -0400 Received: from mail-vx0-f174.google.com ([209.85.220.174]:43139 "EHLO mail-vx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752446Ab1H3WoM (ORCPT ); Tue, 30 Aug 2011 18:44:12 -0400 Date: Wed, 31 Aug 2011 00:44:06 +0200 From: Frederic Weisbecker To: Peter Zijlstra Cc: LKML , Andrew Morton , Anton Blanchard , Avi Kivity , Ingo Molnar , Lai Jiangshan , "Paul E . McKenney" , Stephen Hemminger , Thomas Gleixner , Tim Pepper , Dimitri Sivanich , Paul Menage Subject: Re: [PATCH 12/32] nohz: Try not to give the timekeeping duty to a cpuset nohz cpu Message-ID: <20110830224404.GE15953@somewhere.redhat.com> References: <1313423549-27093-1-git-send-email-fweisbec@gmail.com> <1313423549-27093-13-git-send-email-fweisbec@gmail.com> <1314629745.2816.84.camel@twins> <20110830151704.GV9748@somewhere.redhat.com> <1314718648.5812.20.camel@twins> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1314718648.5812.20.camel@twins> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 30, 2011 at 05:37:28PM +0200, Peter Zijlstra wrote: > On Tue, 2011-08-30 at 17:17 +0200, Frederic Weisbecker wrote: > > On Mon, Aug 29, 2011 at 04:55:45PM +0200, Peter Zijlstra wrote: > > > On Mon, 2011-08-15 at 17:52 +0200, Frederic Weisbecker wrote: > > > > Try to give the timekeeing duty to a CPU that doesn't belong > > > > to any nohz cpuset when possible, so that we increase the chance > > > > for these nohz cpusets to run their CPUs out of periodic tick > > > > mode. > > > > > > You and Dmitiri might want to get together: > > > > > > lkml.kernel.org/r/20110823195628.GB4533@sgi.com > > > > Right! > > > > There is another missing piece in my patchset. If every non adaptive-nohz > > CPUs are sleeping, then none is handling the do_timer duty and adaptive nohz > > CPUs run with a stale jiffies and walltime. > > Doesn't nohz already deal with the case of all cpus being idle? In that > case the cpu that wakes up first gets to play catch up on irq_enter() or > so. Sure and that works for the nohz idle case. But that's not enough anymore in the case of adaptive nohz CPUs. They can run for a while without the tick and if nobody else maintains a tick either then jiffies and walltime are not maintained anymore.