[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140220212854.GO17949@sgi.com>
Date: Thu, 20 Feb 2014 15:28:54 -0600
From: Russ Anderson <rja@....com>
To: Matthew Garrett <matthew.garrett@...ula.com>
Cc: "lenb@...nel.org" <lenb@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"minyard@....org" <minyard@....org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>
Subject: Re: [PATCH V2] Change ACPI IPMI support to "default y"
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@....com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists