Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755639AbaGSS3i (ORCPT ); Sat, 19 Jul 2014 14:29:38 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:58188 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751754AbaGSS3h (ORCPT ); Sat, 19 Jul 2014 14:29:37 -0400 Date: Sat, 19 Jul 2014 20:28:59 +0200 From: Peter Zijlstra To: Frederic Weisbecker Cc: "Paul E. McKenney" , linux-kernel@vger.kernel.org, mingo@kernel.org, laijs@cn.fujitsu.com, dipankar@in.ibm.com, akpm@linux-foundation.org, mathieu.desnoyers@efficios.com, josh@joshtriplett.org, tglx@linutronix.de, rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com, oleg@redhat.com, bobby.prani@gmail.com Subject: Re: [PATCH tip/core/rcu] Do not keep timekeeping CPU tick running for non-nohz_full= CPUs Message-ID: <20140719182859.GJ3935@laptop> References: <20140719165350.GA18411@linux.vnet.ibm.com> <20140719180120.GA20887@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140719180120.GA20887@localhost.localdomain> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Jul 19, 2014 at 08:01:24PM +0200, Frederic Weisbecker wrote: > This can be changed by allowing timekeeping duty from all non-nohz_full CPUs, that's > the initial direction I took, but it involved a lot of complications and scalability > issues. How so, currently any CPU can be timekeeper, how is any !nohz_full cpu different? -- 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/