Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753306AbaDOGEz (ORCPT ); Tue, 15 Apr 2014 02:04:55 -0400 Received: from mail-oa0-f54.google.com ([209.85.219.54]:40637 "EHLO mail-oa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751152AbaDOGEx (ORCPT ); Tue, 15 Apr 2014 02:04:53 -0400 MIME-Version: 1.0 In-Reply-To: <20140414120600.GJ11096@twins.programming.kicks-ass.net> References: <20140410143857.GA27654@localhost.localdomain> <20140411145333.GC3438@localhost.localdomain> <20140411151825.GX11096@twins.programming.kicks-ass.net> <20140414110245.GG11096@twins.programming.kicks-ass.net> <20140414114744.GI11096@twins.programming.kicks-ass.net> <20140414120600.GJ11096@twins.programming.kicks-ass.net> Date: Tue, 15 Apr 2014 11:34:53 +0530 Message-ID: Subject: Re: [Query]: tick-sched: why don't we stop tick when we are running idle task? From: Viresh Kumar To: Peter Zijlstra Cc: Frederic Weisbecker , Thomas Gleixner , Linux Kernel Mailing List , Lists linaro-kernel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14 April 2014 17:36, Peter Zijlstra wrote: > That's a bit of a non-answer. I'm fairly sure its not a gazillion > issues, since the actual scheduler tick doesn't actually do that much. > > So start by enumerating what is actually required. > > The 2), which I suppose you're now trying to implement is I think > entirely the wrong way. The tick really assumes it runs local, moving it > to another CPU is insane. Yeah, I was trying this one :( I still don't have enough knowledge of scheduler and so can't exactly tell what all requires tick to fire a 1 second. @Frederic: Can you please help :) ? -- viresh -- 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/