Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755398AbaGKUPR (ORCPT ); Fri, 11 Jul 2014 16:15:17 -0400 Received: from casper.infradead.org ([85.118.1.10]:42663 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754839AbaGKUPN (ORCPT ); Fri, 11 Jul 2014 16:15:13 -0400 Date: Fri, 11 Jul 2014 22:15:07 +0200 From: Peter Zijlstra To: Christoph Lameter Cc: Frederic Weisbecker , "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, niv@us.ibm.com, tglx@linutronix.de, rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com, dvhart@linux.intel.com, oleg@redhat.com, sbw@mit.edu Subject: Re: [PATCH tip/core/rcu 11/17] rcu: Bind grace-period kthreads to non-NO_HZ_FULL CPUs Message-ID: <20140711201507.GZ20603@laptop.programming.kicks-ass.net> References: <20140707223756.GA7187@linux.vnet.ibm.com> <1404772701-8804-1-git-send-email-paulmck@linux.vnet.ibm.com> <1404772701-8804-11-git-send-email-paulmck@linux.vnet.ibm.com> <20140708152358.GF6571@localhost.localdomain> <20140708154723.GN4603@linux.vnet.ibm.com> <20140708183846.GJ6571@localhost.localdomain> <20140711182541.GF26045@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 Fri, Jul 11, 2014 at 02:05:08PM -0500, Christoph Lameter wrote: > The use case is pretty straightforward because we are trying to keep as > much OS noise as possible off most processors. Processor 0 is the > sacrificial lamb that will be used for all OS processing and hopefully all > high latency operations will occur there. Processors 1-X have a tick but > we still try to keep latencies sane. And then there is X-Y where tick is > off. So the problem is -- and this isn't too hard to create -- when we saturate/overload cpu0 with just the housekeeping. At that point it would be good if we could scale and use multiple housekeepers. -- 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/