Corey Minyard & Randy Dunlap wrote:

Randy>> From what I recall (probably 2 years ago), [older] ipmi hardware
Randy>> does not generate event interrupts, so it has to be polled.
Randy>>
Randy>> Corey, can you elaborate on this?

Corey> Certainly.  Yes, some (probably most) IPMI hardware does not use
Corey> interrupts, and unfortunately, it's not just older machines.
Corey> The driver used to poll more slowly, but in many cases the
Corey> performance was unacceptable.
Corey>
Corey> kipmid is only started if the hardware doesn't support
Corey> interrupts, so only users with sub-standard hardware have to
Corey> suffer with this problem.

Regrettably, of the "big three" in the "PC Server" world, only HP's iLO2
BMC supports interrupts.  Dell's DRAC4 & 5 don't, IBM's ASM, RSA, etc.
don't.  Also (at least out of a sample of one) SuperMicro also doesn't
have an interrupt.

They also have all settled on the KCS interface, which dribbles one
character through per non-interrupt.  So sad.  Dell's DRAC3 had a BT BMC
which transferred whole IPMI packets via DMA _and_ had an interrupt.
HP's ancient SMIC equipment also had an interrupt (but that's also
char-by-char, and their current KCS has an interrupt, so at least they
haven't regressed).  I've guessed that some chip vendor must have
come out with a Really Cheep KCS implementation and drove every other
implementation out of the market.  :-(

I've heard rumors that some current Sun hardware has BT.

>Bela<
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Openipmi-developer mailing list
Openipmi-developer@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openipmi-developer

Reply via email to