Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752700AbbHMMoH (ORCPT ); Thu, 13 Aug 2015 08:44:07 -0400 Received: from mail-wi0-f181.google.com ([209.85.212.181]:38545 "EHLO mail-wi0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752383AbbHMMoF (ORCPT ); Thu, 13 Aug 2015 08:44:05 -0400 Date: Thu, 13 Aug 2015 14:44:02 +0200 From: Frederic Weisbecker To: Peter Zijlstra Cc: Vatika Harlalka , mingo@redhat.com, tglx@linutronix.de, rafael.j.wysocki@intel.com, schwidefsky@de.ibm.com, linux-kernel@vger.kernel.org, preetium@andrew.cmu.edu, preeti.murthy@gmail.com Subject: Re: [PATCH 0/2] nohz_full: Offload task_tick to remote housekeeping cpus for nohz_full cpus Message-ID: <20150813124401.GA29958@lerouge> References: <20150813122223.GC16853@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150813122223.GC16853@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1251 Lines: 23 On Thu, Aug 13, 2015 at 02:22:23PM +0200, Peter Zijlstra wrote: > On Thu, Aug 13, 2015 at 02:55:36PM +0530, Vatika Harlalka wrote: > > This patchset is for offloading task_tick() to a remote housekeeping > > cpu. The larger aim is to stop ticks on nohz_full cpus. For this, extra > > work must be done by housekeeping cpus. So, task_tick is called from a > > delayed workqueue for nohz_full cpus and the work is requeued every second > > for those nohz_full cpus whose ticks are stopped while they are busy. In > > the rest of the cases it will lead to redundant accounting. To facilitate > > this, a new function tick_nohz_remote_tick_stopped is added to indicate > > whether ticks are stopped on a remote cpu. > > Tick related code in core.c is moved to tick.c > > *sigh* of course you didn't read what I've written on this topic.. What is it? Note Vatika wrote this after my suggestion, so if there is an issue, I'm likely the responsible :-) But I don't recall you opposed to this solution. Thanks. -- 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/