From: Andi Kleen <andi@firstfloor.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>, Mike Galbraith <efault@gmx.de>,
Frederik Deweerdt <deweerdt@free.fr>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
suresh.b.siddha@intel.com, Ingo Molnar <mingo@elte.hu>,
jblunck@suse.de
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000002
Date: Tue, 29 Jul 2008 19:50:43 +0200 [thread overview]
Message-ID: <20080729175043.GA11196@one.firstfloor.org> (raw)
In-Reply-To: <20080729102251.22ac8543@infradead.org>
> That's not what datacenter people say. As long as power gain is bigger
> than performance loss.. they tend to want it.
That's a special case. It's fine but they should explicitely configure it.
I suspect even the data center people prefer "opt in" versus "opt out" here.
> Also "significantly" is extremely subjective, like in this case it can
> be a win or a loss, depending.
My impression is that the losses are more likely than the wins here.
>
> > When the user says impacting performance
> > is ok then doing that is fine of course, but not by default.
>
> that's a fine kernel policy.
>
> Distros will override this policy if their users tell them they're
> willing to do the tradeoff.. they will pick that default. In fact..
> that's a big part of their job..
I'm not fully convinced that was done intentionally in this case.
If there's an explicit setting somewhere that's fine anyways, but I think
here it more looks like a mistake.
-Andi
next prev parent reply other threads:[~2008-07-29 17:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 9:53 BUG: unable to handle kernel NULL pointer dereference at 00000002 Aneesh Kumar K.V
2008-07-28 22:26 ` Frederik Deweerdt
2008-07-29 4:22 ` Mike Galbraith
2008-07-29 12:09 ` Andi Kleen
2008-07-29 13:56 ` Arjan van de Ven
2008-07-29 14:53 ` Andi Kleen
2008-07-29 15:30 ` Arjan van de Ven
2008-07-29 16:31 ` Andi Kleen
2008-07-29 17:22 ` Arjan van de Ven
2008-07-29 17:50 ` Andi Kleen [this message]
2008-07-30 9:05 ` Ingo Molnar
2008-07-30 9:26 ` Andrew Morton
2008-07-30 16:31 ` Greg KH
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=20080729175043.GA11196@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=arjan@infradead.org \
--cc=deweerdt@free.fr \
--cc=efault@gmx.de \
--cc=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suresh.b.siddha@intel.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