From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755390AbZIJKLf (ORCPT ); Thu, 10 Sep 2009 06:11:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755358AbZIJKLf (ORCPT ); Thu, 10 Sep 2009 06:11:35 -0400 Received: from brick.kernel.dk ([93.163.65.50]:35559 "EHLO kernel.dk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755348AbZIJKLe (ORCPT ); Thu, 10 Sep 2009 06:11:34 -0400 Date: Thu, 10 Sep 2009 12:11:37 +0200 From: Jens Axboe To: Ingo Molnar Cc: Nikos Chantziaras , Mike Galbraith , Peter Zijlstra , Con Kolivas , linux-kernel@vger.kernel.org Subject: Re: BFS vs. mainline scheduler benchmarks and measurements Message-ID: <20090910101137.GH18599@kernel.dk> References: <1252486344.28645.18.camel@marge.simson.net> <20090909091009.GR18599@kernel.dk> <20090909115429.GY18599@kernel.dk> <20090909122006.GA18599@kernel.dk> <20090909180404.GA11027@elte.hu> <4AA80C1E.2080901@arcor.de> <20090910060824.GF1335@elte.hu> <20090910064059.GA22646@elte.hu> <20090910095457.GD18599@kernel.dk> <20090910100321.GA7922@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090910100321.GA7922@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 10 2009, Ingo Molnar wrote: > > * Jens Axboe wrote: > > > On Thu, Sep 10 2009, Ingo Molnar wrote: > > > > > > * Ingo Molnar wrote: > > > > > > > > However, the interactivity problems still remain. Does that > > > > > mean it's not a latency issue? > > > > > > > > It means that Jens's test-app, which demonstrated and helped us > > > > fix the issue for him does not help us fix it for you just yet. > > > > > > Lemme qualify that by saying that Jens's issues are improved not > > > fixed [he has not re-run with latest latt.c yet] but not all things > > > are fully fixed yet. For example the xmodmap thing sounds > > > interesting - could that be a child-runs-first effect? > > > > I thought so too, so when -tip failed to boot I pulled the patches > > from Mike into 2.6.31. It doesn't change anything for xmodmap, > > though. > > Note, you can access just the pristine scheduler patches by checking > out and testing tip:sched/core - no need to pull them out and apply. > > Your crash looks like clocksource related - that's in a separate > topic which you can thus isolate if you use sched/core. I'm building sched/core now and will run the xmodmap test there. -- Jens Axboe