From: Arjan van de Ven <arjan@linux.intel.com>
To: Corey Minyard <minyard@acm.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
"Kok, Auke" <auke-jan.h.kok@intel.com>,
"discuss@LessWatts.org" <discuss@LessWatts.org>,
"openipmi-developer@lists.sourceforge.net"
<openipmi-developer@lists.sourceforge.net>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Discuss] [PATCH] ipmi: use round_jiffies on timers to reduce timer overhead/wakeups
Date: Thu, 22 Oct 2009 05:57:06 +0900 [thread overview]
Message-ID: <4ADF75A2.50202@linux.intel.com> (raw)
In-Reply-To: <4ADF6D76.7070409@acm.org>
Corey Minyard wrote:
> Certainly. Yes, some (probably most) IPMI hardware does not use
> interrupts, and unfortunately, it's not just older machines. The driver
> used to poll more slowly, but in many cases the performance was
> unacceptable.
... but now it burns quite a bit of power (I'd not be surprised if it is 10 Watts extra on a 70W server)
is there any way to poll slowly until there is active ipmi traffic, during which we can then poll a bit faster.
... and then go back to slow polling when there is an ipmi idle period ?
next prev parent reply other threads:[~2009-10-21 20:57 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
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 [this message]
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=4ADF75A2.50202@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=auke-jan.h.kok@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox