public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: Bela Lubkin <blubkin@vmware.com>
Cc: "'Matt Domsch'" <Matt_Domsch@dell.com>,
	Arjan van de Ven <arjan@linux.intel.com>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"discuss@LessWatts.org" <discuss@LessWatts.org>,
	"openipmi-developer@lists.sourceforge.net" 
	<openipmi-developer@lists.sourceforge.net>
Subject: Re: [Openipmi-developer] [Discuss] [PATCH] ipmi: use	round_jiffies on timers to reduce timer overhead/wakeups
Date: Thu, 22 Oct 2009 15:02:51 -0500	[thread overview]
Message-ID: <4AE0BA6B.50805@acm.org> (raw)
In-Reply-To: <E0AA796A7E3F4C4E8F1065D15FE4786183AF6948@EXCH-MBX-4.vmware.com>

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

  reply	other threads:[~2009-10-22 21:03 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
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 [this message]
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=4AE0BA6B.50805@acm.org \
    --to=minyard@acm.org \
    --cc=Matt_Domsch@dell.com \
    --cc=arjan@linux.intel.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=blubkin@vmware.com \
    --cc=discuss@LessWatts.org \
    --cc=linux-kernel@vger.kernel.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