Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751325AbZCINiS (ORCPT ); Mon, 9 Mar 2009 09:38:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750853AbZCINiD (ORCPT ); Mon, 9 Mar 2009 09:38:03 -0400 Received: from mail.gmx.net ([213.165.64.20]:32819 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750840AbZCINiB (ORCPT ); Mon, 9 Mar 2009 09:38:01 -0400 X-Authenticated: #14349625 X-Provags-ID: V01U2FsdGVkX19I7CtVjWdITIhjndIQNfcuoulymmhduw4fJUrMOe 9sey75dp/NHnQw Subject: Re: [patch] Re: scheduler oddity [bug?] From: Mike Galbraith To: Peter Zijlstra Cc: Ingo Molnar , Balazs Scheidler , linux-kernel@vger.kernel.org, Willy Tarreau In-Reply-To: <1236604563.6027.8.camel@marge.simson.net> References: <1236448069.16726.21.camel@bzorp.balabit> <1236505323.6281.57.camel@marge.simson.net> <1236506309.6972.8.camel@marge.simson.net> <20090308153956.GB19658@elte.hu> <1236529200.7110.16.camel@marge.simson.net> <20090308175255.GA22802@elte.hu> <1236585731.6118.24.camel@marge.simson.net> <20090309080714.GB24904@elte.hu> <1236596664.8389.331.camel@laptop> <1236604563.6027.8.camel@marge.simson.net> Content-Type: text/plain Date: Mon, 09 Mar 2009 14:37:50 +0100 Message-Id: <1236605870.6515.5.camel@marge.simson.net> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1.1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.61 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2416 Lines: 52 On Mon, 2009-03-09 at 14:16 +0100, Mike Galbraith wrote: > On Mon, 2009-03-09 at 12:04 +0100, Peter Zijlstra wrote: > > > OK, talked a bit with Ingo, the reason you're doing is that avg_overlap > > can easily grow stale.. I can see that happen indeed. > > > > So the 'perfect' thing would be a task-runtime decay, barring that the > > preemption thing seems a sane enough hart-beat of a task. > > > > How does the below look to you? > > Other than the fact that the test for sync reject is currently > avg_overlap > sysctl_sched_migration_cost, looks fine to me. Having it > capped at the boundary is probably the better way to go. Heh, doesn't _quite_ work though. The little bugger now hovers just under :-/ pipetest (5976, #threads: 1) --------------------------------------------------------- se.exec_start : 150672.502691 se.vruntime : 94882.186606 se.sum_exec_runtime : 34875.797932 se.avg_overlap : 0.499993 nr_switches : 3680 nr_voluntary_switches : 0 nr_involuntary_switches : 3680 se.load.weight : 1024 policy : 0 prio : 120 clock-delta : 112 pipetest (5977, #threads: 1) --------------------------------------------------------- se.exec_start : 150665.016951 se.vruntime : 94817.157909 se.sum_exec_runtime : 7069.323019 se.avg_overlap : 0.012718 nr_switches : 2931 nr_voluntary_switches : 2930 nr_involuntary_switches : 1 se.load.weight : 1024 policy : 0 prio : 120 clock-delta : 117 -- 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/