Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751714AbaKKRI3 (ORCPT ); Tue, 11 Nov 2014 12:08:29 -0500 Received: from resqmta-po-03v.sys.comcast.net ([96.114.154.162]:39352 "EHLO resqmta-po-03v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751218AbaKKRI1 (ORCPT ); Tue, 11 Nov 2014 12:08:27 -0500 Date: Tue, 11 Nov 2014 11:08:23 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@gentwo.org To: Frederic Weisbecker cc: Thomas Gleixner , linux-kernel@vger.kernel.org, Gilad Ben-Yossef , Tejun Heo , John Stultz , Mike Frysinger , Minchan Kim , Hakan Akkan , Max Krasnyansky , "Paul E. McKenney" , Hugh Dickins , Viresh Kumar , "H. Peter Anvin" , Ingo Molnar , Peter Zijlstra Subject: Re: [NOHZ] Remove scheduler_tick_max_deferment In-Reply-To: <20141111153653.GB3216@lerouge> Message-ID: References: <20141110224306.GC29741@lerouge> <20141111153653.GB3216@lerouge> Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 11 Nov 2014, Frederic Weisbecker wrote: > "there" here is the syscall/exception/interrupt entry path. And like I said, updating > timekeeping from these places is overkill (although we do it in interrupt entry on > dynticks-idle, but we don't have timekeeping when all system is idle). Well that is going to extremes I would think. Lets keep one processor alive so that the rest can be as noise free as possible. -- 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/