public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russ Anderson <rja@sgi.com>
To: Matthew Garrett <matthew.garrett@nebula.com>
Cc: "lenb@kernel.org" <lenb@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"minyard@acm.org" <minyard@acm.org>,
	"rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH V2] Change ACPI IPMI support to "default y"
Date: Thu, 20 Feb 2014 15:28:54 -0600	[thread overview]
Message-ID: <20140220212854.GO17949@sgi.com> (raw)
In-Reply-To: <1392930047.20109.6.camel@x230>

On Thu, Feb 20, 2014 at 09:00:48PM +0000, Matthew Garrett wrote:
> On Thu, 2014-02-20 at 14:59 -0600, Russ Anderson wrote:
> > On Thu, Feb 20, 2014 at 08:46:04PM +0000, Matthew Garrett wrote:
> > > On Thu, 2014-02-20 at 14:40 -0600, Russ Anderson wrote:
> > > 
> > > > This is also a problem for systems with functional BMCs.  Our
> > > > large cluster systems do all IPMI traffic (monitoring) through
> > > > a system controller back door.  We do not want the kernel
> > > > doing IPMI commands on those systems.
> > > 
> > > Why not?
> > 
> > Because some customers want to use cpu cycles for their
> > application and let the ipmi monitoring go on through
> > the system controller network.
> 
> Why is it generating any significant amount of CPU load? We're not
> talking about a high-bandwidth interface here.

For some customers _any_ amount is significant, especially
on large clustered systems where the amount is multiplied
by tens or hundreds of thousands of nodes.

You many not think wasting their cpu cycles is important, but they do.


-- 
Russ Anderson,  Kernel and Performance Software Team Manager
SGI - Silicon Graphics Inc          rja@sgi.com

  reply	other threads:[~2014-02-20 21:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 16:28 [PATCH V2] Change ACPI IPMI support to "default y" Matthew Garrett
2014-02-18 23:26 ` Rafael J. Wysocki
2014-02-18 23:15   ` Matthew Garrett
2014-02-18 23:35     ` Rafael J. Wysocki
2014-02-18 23:25       ` Matthew Garrett
2014-02-19  0:45         ` Rafael J. Wysocki
2014-02-19  0:53           ` Corey Minyard
2014-03-12 23:00     ` Pavel Machek
2014-03-12 23:22       ` Matthew Garrett
2014-03-13  7:22         ` Pavel Machek
2014-03-13  7:24           ` Matthew Garrett
2014-03-13  8:38             ` Pavel Machek
2014-03-13 13:29               ` Corey Minyard
2014-03-16  8:53                 ` Pavel Machek
2014-02-20 20:14 ` Russ Anderson
2014-02-20 20:16   ` Matthew Garrett
2014-02-20 20:40     ` Russ Anderson
2014-02-20 20:46       ` Matthew Garrett
2014-02-20 20:59         ` Russ Anderson
2014-02-20 21:00           ` Matthew Garrett
2014-02-20 21:28             ` Russ Anderson [this message]
2014-02-20 21:39               ` Matthew Garrett
2014-02-20 22:06                 ` Russ Anderson
2014-02-20 22:26                   ` Matthew Garrett
2014-02-20 22:45                     ` Russ Anderson
2014-02-20 23:09                       ` Matthew Garrett
2014-02-20 23:59                         ` Russ Anderson
2014-02-21  0:13                           ` Matthew Garrett
2014-02-21 16:53                             ` Russ Anderson
2014-02-21  2:17                           ` Zheng, Lv
2014-02-21 16:12                             ` Matthew Garrett
2014-02-24  0:48                               ` Zheng, Lv
2014-02-21 16:33                             ` Russ Anderson
2014-02-21 13:37             ` Corey Minyard
2014-02-21 15:51               ` Matthew Garrett
2014-02-21 17:12                 ` Corey Minyard
2014-02-20 21:49         ` Russ Anderson
2014-02-20 21:51           ` Matthew Garrett
2014-02-21  0:10   ` Rafael J. Wysocki
2014-02-20 23:01 ` Russ Anderson

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=20140220212854.GO17949@sgi.com \
    --to=rja@sgi.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=minyard@acm.org \
    --cc=rjw@rjwysocki.net \
    /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