Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751584AbaKKO6k (ORCPT ); Tue, 11 Nov 2014 09:58:40 -0500 Received: from resqmta-po-09v.sys.comcast.net ([96.114.154.168]:55240 "EHLO resqmta-po-09v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751344AbaKKO6j (ORCPT ); Tue, 11 Nov 2014 09:58:39 -0500 Date: Tue, 11 Nov 2014 08:58:35 -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: <20141110224306.GC29741@lerouge> Message-ID: References: <20141110224306.GC29741@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 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? -- 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/