[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6693458.1220717142061.kamezawa.hiroyu@jp.fujitsu.com>
Date: Sun, 7 Sep 2008 01:05:42 +0900 (JST)
From: kamezawa.hiroyu@...fujitsu.com
To: kamezawa.hiroyu@...fujitsu.com
Cc: Ingo Molnar <mingo@...e.hu>, Yasunori Goto <y-goto@...fujitsu.com>,
Andi Kleen <andi@...stfloor.org>,
Gary Hade <garyhade@...ibm.com>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Badari Pulavarty <pbadari@...ibm.com>,
Mel Gorman <mel@....ul.ie>, Chris McDermott <lcm@...ibm.com>,
linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: Re: Re: [PATCH] [RESEND] x86_64: add memory hotremove config option
----- Original Message -----
>>Having said that, i have my doubts about its generic utility (the power
>>saving aspects are likely not realizable - nobody really wants DIMMs to
>>just sit there unused and the cost of dynamic migration is just
>>horrendous) - but as long as it's opt-in there's no reason to limit the
>>availability of an in-kernel feature artificially.
>
>Nobody ? maybe just a trade-off problem in user side.
>Even without DIMM hotplug or DIMM's power save mode, making a DIMM idle
>is of no use ? I think memory consumes much power when it used.
>Memory Hotplug and ZONE_MOVABLE can make some memory idle.
>(I'm sorry if my thinking is wrong.)
>
But I have to point out HDD access consumes far power than memory.
That's trade-off problem depends on usage, anyway.
Thanks,
-Kame
--
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