From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753257AbXC2G3P (ORCPT ); Thu, 29 Mar 2007 02:29:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753278AbXC2G3P (ORCPT ); Thu, 29 Mar 2007 02:29:15 -0400 Received: from mail.gmx.net ([213.165.64.20]:36031 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1753257AbXC2G3O (ORCPT ); Thu, 29 Mar 2007 02:29:14 -0400 X-Authenticated: #14349625 X-Provags-ID: V01U2FsdGVkX1/77mJ299X7yhukj+q6gOa41k5fNQwa7G8Z+mgQzP IHsNTNaeFVX30H Subject: Re: [PATCH] sched: staircase deadline misc fixes From: Mike Galbraith To: Con Kolivas Cc: Ingo Molnar , linux list , Andrew Morton , ck list In-Reply-To: <1175147455.6430.91.camel@Homer.simpson.net> References: <200703290237.38777.kernel@kolivas.org> <20070328184843.GA17420@elte.hu> <200703290944.45888.kernel@kolivas.org> <1175147455.6430.91.camel@Homer.simpson.net> Content-Type: text/plain Date: Thu, 29 Mar 2007 08:29:10 +0200 Message-Id: <1175149750.6430.110.camel@Homer.simpson.net> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2007-03-29 at 07:50 +0200, Mike Galbraith wrote: > Opinion polls are nice, but I'm more interested in gathering numbers > which either validate or invalidate the claims of the design documents. Suggestion: try the testcase that Satoru Takeuch posted. The numbers I got with latest SD were no better than the numbers I got with the patch I posted to try to solve it. Seems to me the numbers with SD should have been much better, but they in fact were not. Running that thing, mainline's GUI was not usable, even with my patch, but neither was it usable with SD. What's the difference between horrible with mainline and merely terrible with SD? In both, the GUI ends up doing round-robin with a slew of hogs. In mainline, this happens because the history logic can and does get it wrong sometimes, which this exploit deliberately triggers. With SD, it's by design. -Mike