From: Stephane Eranian <eranian@hpl.hp.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] x86_64 add missing enter_idle() calls
Date: Mon, 16 Oct 2006 07:44:17 -0700 [thread overview]
Message-ID: <20061016144417.GG15540@frankl.hpl.hp.com> (raw)
In-Reply-To: <200610161636.52721.ak@suse.de>
On Mon, Oct 16, 2006 at 04:36:52PM +0200, Andi Kleen wrote:
>
> > With the original code, the number of callbacks you see for IDLE_START and
> > IDLE_STOP is not too obvious.
> >
> > On an idle system Opteron 250 with HZ=250, one would expect to see for a 10s duration:
> > - for CPU0 : IDLE_START = IDLE_STOP = about 5000 calls
> > - for other CPUs: IDLE_START = IDLE_STOP = about 2500 calls
>
> Yes.
>
> > With the original code, you get the following number of calls:
> >
> > CPU0.IDLE_START = 44 (enter_idle)
> > CPU0.IDLE_STOP = 5206 (exit_idle)
> >
> > CPU1.IDLE_START = 27 (enter_idle)
> > CPU1.IDLE_STOP = 2528 (exit_idle)
> >
> > Now, of course, you may get "batched" interrupts where you do not return to idle
> > before you process the next interrupt. But the difference seems quite high here.
>
> Shouldn't happen for timer interrupts.
> >
> > Do you have an explanation for this?
>
> Hmm, the last time I fixed this when you complained (post .18) i added a counter for
> entry/exit and verified that it was balanced. I haven't rechecked since then.
> I don't know why your numbers are off. You're using the latest git tree, right?
>
No, I am still using 2.6.18. I saw your change in git (thanks for that). I need to try
with this tree and see what happens.
Thanks.
--
-Stephane
next prev parent reply other threads:[~2006-10-16 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 8:16 Stephane Eranian
2006-10-16 10:08 ` Andi Kleen
2006-10-16 14:13 ` Stephane Eranian
2006-10-16 14:36 ` Andi Kleen
2006-10-16 14:44 ` Stephane Eranian [this message]
2006-10-17 16:47 ` Stephane Eranian
2006-10-21 9:18 ` Stephane Eranian
2006-10-21 13:22 ` Andi Kleen
2006-10-24 10:00 ` Stephane Eranian
2006-10-25 21:29 ` Stephane Eranian
2006-10-27 16:03 ` Andi Kleen
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=20061016144417.GG15540@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.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®