Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751307AbaKKPhA (ORCPT ); Tue, 11 Nov 2014 10:37:00 -0500 Received: from mail-wg0-f41.google.com ([74.125.82.41]:45257 "EHLO mail-wg0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750859AbaKKPg7 (ORCPT ); Tue, 11 Nov 2014 10:36:59 -0500 Date: Tue, 11 Nov 2014 16:36:55 +0100 From: Frederic Weisbecker To: Christoph Lameter 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 Message-ID: <20141111153653.GB3216@lerouge> References: <20141110224306.GC29741@lerouge> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 On Tue, Nov 11, 2014 at 08:58:35AM -0600, Christoph Lameter wrote: > On Mon, 10 Nov 2014, Frederic Weisbecker wrote: > > > Ok, I confess we moved part of that housekeeping to the syscall/exception/interrupt > > entry path. We did that for cputime accounting and RCU. And it's possible to > > even do that for timekeeping. But then the kernel entrypoint is going to be extremely > > costly. It's worth CPU 0 as a sacrificial lamb. > > Well we can redirect to the scheduler setting the task flag and handle > costly stuff there if necessary? "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). -- 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/