Re: [Openipmi-developer] [Discuss] [PATCH] ipmi: use round_jiffies ontimers to reduce timer overhead/wakeups
From: Corey Minyard
Date: Thu Oct 22 2009 - 17:03:35 EST
Bela Lubkin wrote:
Matt Domsch wrote:
Though I'm really curious that HP has a KCS+interrupt controller
available. That gives me hope that the industry-wide problems which
prevented Dell from doing likewise a couple years ago are now
resolved. I'll have my team look into it again.
Can you expand on "industry-wide problems"? (Forced to share
interrupts with a high rate device? Design your gizmo to
support MSI/MSI-x. Add MSI support to ipmi_si if necessary...)
As far as I can tell, HP has never shipped an interrupt-less
BMC. Their current iLO2 BMC is KCS + interrupt. Their older
design was SMIC + interrupt.
Why does everyone use KCS when BT is obviously better? Can
you have your team look into that as well? (Among the various
goals here, I assume that BT -- with a single interrupt and a
DMA transfer instead of shuffling bytes over I/O ports -- would
cost less power. Not that the members of that list will
receive this message: it bounces nonmembers.)
This is an industry where pennies matter, apparently.
My personal preference would be to use the I2C based standard
interface. That actually doesn't perform too badly, it's probably
cheaper than KCS since you already have I2C, anyway, and the I2C
interfaces are generally tied to an interrupt. The trouble is that the
only hardware implementation of this I know of seems to be poorly done,
but that mostly affects trying to use the ethernet interface and the
local interface at the same time.
Of course, the driver for I2C is not yet in the standard kernel as it
requires a fairly massive I2C driver rewrite to allow the IPMI driver to
do it's panic-time operations.
BT would be better for performance, I guess, but it's yet another
interface to tie in, and hanging this off an existing bus seems like a
sensible thing to do. And performance is really not an issue for IPMI.
-corey
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/