From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] ia64 add idle loop entry/exit notifier
Date: Thu, 16 Nov 2006 16:58:25 +0000 [thread overview]
Message-ID: <20061116165825.GH18162@frankl.hpl.hp.com> (raw)
In-Reply-To: <20061115222334.GE17238@frankl.hpl.hp.com>
Ken,
On Wed, Nov 15, 2006 at 06:07:19PM -0800, Chen, Kenneth W wrote:
> Stephane Eranian wrote on Wednesday, November 15, 2006 2:24 PM
> > Here is a patch which adds an idle notifier to IA-64. It clones
> > the one in X86-64. You can register a callback via the notifier
> > and you get called when:
> > - entering the lowest level of the idle loop
> > - exiting the lowest level of the idle loop, either normally
> > or to process an interrupt
> >
> > Basically, you can monitor useful vs. useless work accomplished
> > by the idle thread on each processor.
>
> Is idle notifier a light weight callback thingy? I happen to work
Well, it uses the notifier interface. I have not changed this part.
> on an application environment that cycles CPUs into gazillion nano
> second sleep due to tons of sleep / wake up activity from thousands
> of processes. I'm just checking and hope this notifier chain isn't
> going to add significant overhead when cycling through busy/idle.
>
I would suggest you measure the overhead when no callback
is registered. The patch is such that there will systematically be a
callback registered for SGI machines. But if you are cycling busy/idle,
I would think that you biggest cost if coming out of PAL_HALT.
--
-Stephane
prev parent reply other threads:[~2006-11-16 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 22:23 [PATCH] ia64 add idle loop entry/exit notifier Stephane Eranian
2006-11-16 2:07 ` Chen, Kenneth W
2006-11-16 16:58 ` Stephane Eranian [this message]
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=20061116165825.GH18162@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=linux-ia64@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