Return-Path: <linux-kernel-owner+w=401wt.eu-S1755472AbZIJLfP@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755472AbZIJLfP (ORCPT <rfc822;w@1wt.eu>);
	Thu, 10 Sep 2009 07:35:15 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753755AbZIJLfO
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Thu, 10 Sep 2009 07:35:14 -0400
Received: from brick.kernel.dk ([93.163.65.50]:38042 "EHLO kernel.dk"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1754592AbZIJLfO (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Thu, 10 Sep 2009 07:35:14 -0400
Date: Thu, 10 Sep 2009 13:35:16 +0200
From: Jens Axboe <jens.axboe@oracle.com>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>, Nikos Chantziaras <realnc@arcor.de>,
       Peter Zijlstra <a.p.zijlstra@chello.nl>,
       Con Kolivas <kernel@kolivas.org>, linux-kernel@vger.kernel.org
Subject: Re: BFS vs. mainline scheduler benchmarks and measurements
Message-ID: <20090910113516.GP18599@kernel.dk>
References: <20090910064059.GA22646@elte.hu> <20090910095457.GD18599@kernel.dk> <20090910100321.GA7922@elte.hu> <20090910101137.GH18599@kernel.dk> <20090910102837.GJ18599@kernel.dk> <1252580251.18659.10.camel@marge.simson.net> <20090910110912.GL18599@kernel.dk> <1252581670.18659.11.camel@marge.simson.net> <20090910112443.GN18599@kernel.dk> <1252582108.18659.12.camel@marge.simson.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1252582108.18659.12.camel@marge.simson.net>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1702
Lines: 45

On Thu, Sep 10 2009, Mike Galbraith wrote:
> On Thu, 2009-09-10 at 13:24 +0200, Jens Axboe wrote:
> > On Thu, Sep 10 2009, Mike Galbraith wrote:
> 
> > > xmodmap doesn't seem to be running in this sample.
> > 
> > That's weird, it was definitely running. I did:
> > 
> > sleep 1; xmodmap .xmodmap-carl
> > 
> > in one xterm, and then switched to the other and ran the sched_debug
> > dump. I have to do it this way, as X will not move focus once xmodmap
> > starts running. It could be that xmodmap is mostly idle, and the real
> > work is done by Xorg and/or xfwm4 (my window manager).
> 
> Hm.  Ok, I'll crawl over it, see if anything falls out.

That seems to be confirmed with the low context switch rate of the perf
stat of xmodmap. If I run perf stat -a to get a system wide collection
for xmodmap, I get:

 Performance counter stats for 'xmodmap .xmodmap-carl':

   20112.060925  task-clock-msecs         #      1.998 CPUs 
         629360  context-switches         #      0.031 M/sec
              8  CPU-migrations           #      0.000 M/sec
          13489  page-faults              #      0.001 M/sec
  <not counted>  cycles                  
  <not counted>  instructions            
  <not counted>  cache-references        
  <not counted>  cache-misses            

   10.067532449  seconds time elapsed

And again, system is idle while this is happening. Can't rule out that
this is some kind of user space bug of course.

-- 
Jens Axboe

--
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/