Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751827AbbKJAUN (ORCPT ); Mon, 9 Nov 2015 19:20:13 -0500 Received: from mga09.intel.com ([134.134.136.24]:47243 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751400AbbKJAUL (ORCPT ); Mon, 9 Nov 2015 19:20:11 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,267,1444719600"; d="scan'208";a="681782401" Date: Mon, 9 Nov 2015 16:19:16 -0800 From: Jacob Pan To: Jacob Pan Cc: Peter Zijlstra , Thomas Gleixner , LKML , Arjan van de Ven , Paul Turner , Len Brown , Srinivas Pandruvada , Tim Chen , Andi Kleen , Rafael Wysocki Subject: Re: [RFC PATCH 3/3] sched: introduce synchronized idle injection Message-ID: <20151109161916.1400a0b4@icelake> In-Reply-To: <20151106154929.39aa6701@icelake> References: <1446509428-5616-1-git-send-email-jacob.jun.pan@linux.intel.com> <1446509428-5616-4-git-send-email-jacob.jun.pan@linux.intel.com> <20151103133120.GD17308@twins.programming.kicks-ass.net> <20151105135952.GE11639@twins.programming.kicks-ass.net> <20151105153625.25fbfe69@icelake> <20151106074510.GM3604@twins.programming.kicks-ass.net> <20151106154929.39aa6701@icelake> Organization: OTC X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.23; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1141 Lines: 26 On Fri, 6 Nov 2015 15:49:29 -0800 Jacob Pan wrote: > > Check the softirq stuff before calling throttle ? > > yes, played with it but it seems there are other cases causing pending > softirq in idle in addition to throttle. I still haven't figure it > out, this problem only shows up in heavy irq, network load. e.g. > compile kernel over NFS. Debugging. ok, I added a check for softirq_pending and a retry. seems to work. Now idle injection will allow softirq and softirqd to run. The caveat is that during that injection period, if softirqd does not run for the entire duration, other normal tasks would also run during forced idle. But just for that period. I guess we have to strike for the right balance for QoS and overhead. For most workload, pending softirq is rare so the tasks slip under softirqd are also rare. Will send out V2 soon. Thanks, Jacob -- 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/