All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andi Kleen <andi@firstfloor.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>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000002
Date: Tue, 29 Jul 2008 10:22:51 -0700	[thread overview]
Message-ID: <20080729102251.22ac8543@infradead.org> (raw)
In-Reply-To: <20080729163113.GP30344@one.firstfloor.org>

On Tue, 29 Jul 2008 18:31:13 +0200
Andi Kleen <andi@firstfloor.org> wrote:

> > > A power saving feature that has a significant trade off between
> > > power and performance. 
> > 
> > do you have numbers to explain "significant tradeoff" ?
> 
> I don't have numbers, but from the theory it seems pretty clear. 
> When you e.g. have two processes with 6MB cache foot print and 
> you have two 2C CPUs with 6MB cache they will fit in cache, but 
> with power aware scheduler they won't because both processes will run
> on the single 6MB package.  With NUMA the effect is even worse because
> also the memory controllers are not used evenly.
> And there's the FSB bandwidth, but that's a secondary issue.

but if you have 2 threads that share a lot of data, it's the opposite.

Or if you have a bunch of things which are smaller than the cache... 
(and they do share, for example glibc will be largely shared).

it's not a clear heavy loss, it's one of those "depends" cases.
(which sucks)

> > 
> >  
> > > This means performance will go down. Perhaps it would be ok on
> > > battery, 
> > 
> > the illusion that power only matters on battery got buried a few
> > years ago ;)
> 
> My understanding was always that unless you're on battery power saving
> features that are enabled by default are not supposed to impact
> performance significantly. 

That's not what datacenter people say. As long as power gain is bigger
than performance loss.. they tend to want it.

Also "significantly" is extremely subjective, like in this case it can
be a win or a loss, depending.

> 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.. 


-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-29 17:23 UTC|newest]

Thread overview: 14+ 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 [this message]
2008-07-29 17:50                 ` Andi Kleen
2008-07-30  9:05     ` Ingo Molnar
2008-07-30  9:26       ` Andrew Morton
2008-07-30 16:31         ` Greg KH
  -- strict thread matches above, loose matches on Subject: below --
2012-06-14 17:45 Pierre-Philipp Braun

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=20080729102251.22ac8543@infradead.org \
    --to=arjan@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=deweerdt@free.fr \
    --cc=efault@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.