[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1309370342.11430.604.camel@nimitz>
Date: Wed, 29 Jun 2011 10:59:02 -0700
From: Dave Hansen <dave@...ux.vnet.ibm.com>
To: Ankita Garg <ankita@...ibm.com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
svaidy@...ux.vnet.ibm.com, thomas.abraham@...aro.org,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
Matthew Garrett <mjg59@...f.ucam.org>,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH 00/10] mm: Linux VM Infrastructure to support Memory
Power Management
On Wed, 2011-06-29 at 23:12 +0530, Ankita Garg wrote:
> 4. The kernel must have a mechanism to maintain utilization
> statistics pertaining to a piece of hardware, so that it can
> trigger the hardware to power it off
Having statistics like this would certainly be nice, but how important
_is_ it? Is it really a show-stopper? There's some stuff today, like
the NPT/EPT support in KVM where we don't even have visibility in to
when a given page is referenced.
It's also going to be a pain to track kernel references. On x86, our
kernel linear mapping uses 1GB pages when it can, and those are greater
than the 512MB granularity that we've been talking about here. It's
even larger on powerpc. I'm also pretty sure we don't even _look_ at
the referenced bits in the kernel page tables. We'll definitely need
some infrastructure to do that.
> 5. Being able to group these pieces of hardware for purpose of
> higher savings.
Do you really mean group, or do you mean "turn as many off as possible"?
-- Dave
--
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