From: Matthew Garrett <matthew.garrett@nebula.com>
To: "rja@sgi.com" <rja@sgi.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 21:39:23 +0000 [thread overview]
Message-ID: <1392932363.20109.11.camel@x230> (raw)
In-Reply-To: <20140220212854.GO17949@sgi.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1149 bytes --]
On Thu, 2014-02-20 at 15:28 -0600, Russ Anderson wrote:
> 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.
Then they should be running locally built kernels in order to ensure
that there's no problematic code running at all. Distribution kernels
will always contain code that some customers won't be interested in, and
some of that code will end up executing.
If you have specific bug reports, that would be helpful. But you're not
describing actual failure conditions or showing any willingness to
figure out what the underlying problem is. The BMC is generating
messages and handing them off to the host. If that's taking more than a
tiny number of cycles, why? Once we know the answer to that, we can
actually put some effort into fixing it.
--
Matthew Garrett <matthew.garrett@nebula.com>
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-02-20 21:39 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
2014-02-20 21:39 ` Matthew Garrett [this message]
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=1392932363.20109.11.camel@x230 \
--to=matthew.garrett@nebula.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=rja@sgi.com \
--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