From: David Miller <davem@davemloft.net>
To: kjwinchester@gmail.com
Cc: mingo@elte.hu, elendil@planet.nl, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
a.p.zijlstra@chello.nl, efault@gmx.de, richie@coderworld.net,
rjw@sisk.pl
Subject: Re: [git pull] scheduler changes for v2.6.26
Date: Tue, 22 Apr 2008 03:49:35 -0700 (PDT) [thread overview]
Message-ID: <20080422.034935.134139117.davem@davemloft.net> (raw)
In-Reply-To: <480DB2DB.9040908@gmail.com>
From: Kevin Winchester <kjwinchester@gmail.com>
Date: Tue, 22 Apr 2008 06:41:47 -0300
> kevin@alekhine:~/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@maramba:~$ /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?
next prev parent reply other threads:[~2008-04-22 10:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 18:13 Ingo Molnar
2008-04-19 18:47 ` Guillaume Chazarain
2008-04-19 18:49 ` Ingo Molnar
2008-04-19 18:54 ` Peter Zijlstra
2008-04-19 19:47 ` Frans Pop
2008-04-21 12:39 ` Ingo Molnar
2008-04-21 16:31 ` Frans Pop
2008-04-21 19:43 ` Ingo Molnar
2008-04-22 8:51 ` Mike Galbraith
2008-04-22 8:59 ` Ingo Molnar
2008-04-22 9:59 ` Peter Zijlstra
2008-04-22 12:25 ` Mike Galbraith
2008-04-23 8:11 ` Mike Galbraith
2008-04-23 10:30 ` Mike Galbraith
2008-04-23 11:21 ` Peter Zijlstra
2008-04-23 13:27 ` Mike Galbraith
2008-04-22 9:41 ` Kevin Winchester
2008-04-22 10:49 ` David Miller [this message]
2008-04-22 11:10 ` Peter Zijlstra
2008-04-23 9:36 ` Frans Pop
2008-04-23 9:42 ` Peter Zijlstra
2008-04-23 9:46 ` Ingo Molnar
2008-04-23 13:36 ` Frans Pop
2008-04-29 12:29 ` Ingo Molnar
2008-04-29 15:28 ` Steven Rostedt
2008-04-23 16:23 ` Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080422.034935.134139117.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=efault@gmx.de \
--cc=elendil@planet.nl \
--cc=kjwinchester@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=richie@coderworld.net \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®