[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080422.034935.134139117.davem@davemloft.net>
Date: Tue, 22 Apr 2008 03:49:35 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: kjwinchester@...il.com
Cc: mingo@...e.hu, elendil@...net.nl, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
a.p.zijlstra@...llo.nl, efault@....de, richie@...erworld.net,
rjw@...k.pl
Subject: Re: [git pull] scheduler changes for v2.6.26
From: Kevin Winchester <kjwinchester@...il.com>
Date: Tue, 22 Apr 2008 06:41:47 -0300
> kevin@...khine:~/linux$ ./watch-rq-clock.sh
> 89.986517
> 81.033471
> 76.942776
> 90.986318
> 75.988551
> 85.987089
> 74.988696
> 85.987078
> 73.988858
> 88.986641
> 68.989600
The results on my 128-cpu Niagara2 box are even more interesting:
davem@...amba:~$ /bin/bash ./watch-rq-clock.sh
0
0
0
0
0
0
0
0
0
0
0
0
0
...
I guess this script doesn't work correctly when the cpu
whose clock value it greps out of /proc/sched_debug is
in NOHZ mode?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists