Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270321AbTG1R3J (ORCPT ); Mon, 28 Jul 2003 13:29:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270326AbTG1R3J (ORCPT ); Mon, 28 Jul 2003 13:29:09 -0400 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:45572 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id S270321AbTG1R3G (ORCPT ); Mon, 28 Jul 2003 13:29:06 -0400 Date: Mon, 28 Jul 2003 10:33:36 -0700 (PDT) From: Andre Hedrick To: Mike Galbraith cc: Felipe Alfaro Solana , Ingo Molnar , LKML Subject: Re: [patch] sched-2.6.0-test1-G6, interactivity changes In-Reply-To: <5.2.1.1.2.20030728091801.01b83538@pop.gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2539 Lines: 72 No, it was an attempt to get you to explain in detail for people to understand why jitter responses in X have anything with scheduling. Now the a pipe ipc that makings loading go south is interesting. > >Don't bother replying cause last thing I want to know is why. Means, don't tell me about "X becomes extremely jerky", disclose that is below creating the observed effects. -a On Mon, 28 Jul 2003, Mike Galbraith wrote: > At 11:45 PM 7/27/2003 -0700, Andre Hedrick wrote: > > >On Mon, 28 Jul 2003, Mike Galbraith wrote: > > > > > At 09:18 PM 7/27/2003 +0200, Felipe Alfaro Solana wrote: > > > >On Sun, 2003-07-27 at 15:40, Ingo Molnar wrote: > > > > > my latest scheduler patchset can be found at: > > > > > > > > > > redhat.com/~mingo/O(1)-scheduler/sched-2.6.0-test1-G6 > > > > > > > > > > this version takes a shot at more scheduling fairness - i'd be > > interested > > > > > how it works out for others. > > > > > > > >This -G6 patch is fantastic, even without nicing the X server. I didn't > > > >even need to tweak any kernel scheduler knob to adjust for maximum > > > >smoothness on my desktop. Response times are impressive, even under > > > >heavy load. Great! > > > > > > Can you try the following please? > > > > > > This one I just noticed: > > > 1. start top. > > > 2. start dd if=/dev/zero | dd of=/dev/null > > > 3. wiggle a window very briefly. > > > Here, X becomes extremely jerky, and I think this is due to two > > > things. One, X uses it's sleep_avg very quickly, and expires. Two, the > > > piped dd now is highly interactive due to the ns resolution clock (uhoh). > > > >What kind of LAME test is this? If "X becomes extremely jerky" ? > > Huh? The point is that piped cpu hogs just became high priority. > > >Sheesh, somebody come up with a build class solution. > > > >CONFIG_SERVER > >CONFIG_WORKSTATION > >CONGIG_IAMAGEEKWHOPLAYSGAMES > >CONFIG_GENERIC_LAMER > > > >Determining quality of the scheduler based on how a mouse responds is ... > > > >Sorry but this is just laughable, emperical subjective determination > >based on a random hardware combinations for QA/QC for a test? > > > >Don't bother replying cause last thing I want to know is why. > > Oh, I see, you just felt like doing some mindless flaming. > > -Mike > - 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/