From: Arjan van de Ven <arjan@linux.intel.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: discuss@LessWatts.org, lkml <linux-kernel@vger.kernel.org>,
Corey Minyard <minyard@acm.org>,
openipmi-developer@lists.sourceforge.net
Subject: Re: [PATCH] ipmi: use round_jiffies on timers to reduce timer overhead/wakeups
Date: Wed, 21 Oct 2009 11:42:10 -0700 [thread overview]
Message-ID: <20091021114210.4d7e1ea9@linux.intel.com> (raw)
In-Reply-To: <20091021102822.5b32b2dc.randy.dunlap@oracle.com>
On Wed, 21 Oct 2009 10:28:22 -0700
Randy Dunlap <randy.dunlap@oracle.com> wrote:
> From: Randy Dunlap <randy.dunlap@oracle.com>
>
> Use a round_jiffies() variant to reduce overhead of timer
> wakeups. This causes the ipmi timers to occur at the same
> time as other timers (per CPU).
>
> Typical powertop for /ipmi/ (2.6.31, before patch):
> 11.4% (247.4) kipmi0 : __mod_timer (process_timeout)
> 0.6% ( 13.1) <interrupt> : ipmi_si
> 0.5% ( 10.0) <kernel core> : __mod_timer (ipmi_timeout)
>
> powertop for /ipmi/, 2.6.31, after patch:
> 10.8% (247.6) kipmi0 : __mod_timer (process_timeout)
> 0.3% ( 6.9) <interrupt> : ipmi_si
> 0.0% ( 1.0) <kernel core> : __mod_timer (ipmi_timeout)
while it is nice that ipmi_si ande the timer wake up less now.... it's
still rather sad that the 247.6 from kipmi0 are still there..... those
are a much much bigger issue
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-10-21 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 17:28 [PATCH] ipmi: use round_jiffies on timers to reduce timer overhead/wakeups Randy Dunlap
2009-10-21 18:42 ` Arjan van de Ven [this message]
2009-10-21 18:49 ` [Discuss] " Kok, Auke
2009-10-21 20:03 ` Randy Dunlap
2009-10-21 20:22 ` Corey Minyard
2009-10-21 20:57 ` Arjan van de Ven
2009-10-22 2:50 ` Matt Domsch
2009-10-22 16:45 ` Corey Minyard
2009-10-22 19:12 ` [Openipmi-developer] [Discuss] [PATCH] " Bela Lubkin
2009-10-22 20:02 ` Corey Minyard
2009-10-22 22:16 ` Bela Lubkin
2009-10-21 23:46 ` Bela Lubkin
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=20091021114210.4d7e1ea9@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=discuss@LessWatts.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=randy.dunlap@oracle.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.