All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Ferenc Wagner <wferi@niif.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	openipmi-developer@lists.sourceforge.net,
	linux-kernel@vger.kernel.org
Subject: Re: [Openipmi-developer] modprobe ipmi_si hangs under 2.6.30-rc5
Date: Thu, 21 May 2009 07:37:03 -0500	[thread overview]
Message-ID: <4A154AEF.506@acm.org> (raw)
In-Reply-To: <878wkqpz2n.fsf@tac.ki.iif.hu>

Ferenc Wagner wrote:
> Corey Minyard <minyard@acm.org> writes:
>
>   
>> Ferenc Wagner wrote:
>>
>>     
>>> Just out of interest, how often does the driver wake up to check
>>> the inteface?
>>>       
>> When idle, the driver wakes up every 10ms to check for something on
>> the driver.
>>     
>
> Wow, 100 times per second, that sure sounds gross for piping out SEL
> entries!  Though it certainly doesn't matter much for our servers, but
> hasn't it got the potential to heavily tax laptop batteries?  Or is
> that why ipmi_si isn't loaded automatically by udev?
>   
IPMI is used for a lot of things beyond just getting SEL entries.  I 
some cases (probably most) it's excessive, in others it's not.

However, AFAIK IPMI hardware is only available in server systems.  I 
don't think it's ever been used in a laptop.

-corey

  reply	other threads:[~2009-05-21 12:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-12 21:28 modprobe ipmi_si hangs under 2.6.30-rc5 Ferenc Wagner
2009-05-17  0:09 ` Andrew Morton
2009-05-18 17:33   ` Ferenc Wagner
2009-05-18 18:40     ` [Openipmi-developer] " Corey Minyard
2009-05-19  6:26       ` Ferenc Wagner
2009-05-19 21:38         ` Corey Minyard
2009-05-20 16:15           ` Ferenc Wagner
2009-05-20 16:34             ` Corey Minyard
2009-05-21  9:47               ` Ferenc Wagner
2009-05-21 12:37                 ` Corey Minyard [this message]
2009-05-27 12:10                 ` 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=4A154AEF.506@acm.org \
    --to=minyard@acm.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=wferi@niif.hu \
    /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.