Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754614Ab3IZBOW (ORCPT ); Wed, 25 Sep 2013 21:14:22 -0400 Received: from mga09.intel.com ([134.134.136.24]:57611 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751070Ab3IZBOV (ORCPT ); Wed, 25 Sep 2013 21:14:21 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.90,982,1371106800"; d="scan'208";a="383632852" Message-ID: <52438A6B.30202@linux.intel.com> Date: Wed, 25 Sep 2013 18:14:19 -0700 From: Arjan van de Ven User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Andi Kleen CC: Andrew Morton , "Srivatsa S. Bhat" , mgorman@suse.de, dave@sr71.net, hannes@cmpxchg.org, tony.luck@intel.com, matthew.garrett@nebula.com, riel@redhat.com, srinivas.pandruvada@linux.intel.com, willy@linux.intel.com, kamezawa.hiroyu@jp.fujitsu.com, lenb@kernel.org, rjw@sisk.pl, gargankita@gmail.com, paulmck@linux.vnet.ibm.com, svaidy@linux.vnet.ibm.com, isimatu.yasuaki@jp.fujitsu.com, santosh.shilimkar@ti.com, kosaki.motohiro@gmail.com, linux-pm@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [Results] [RFC PATCH v4 00/40] mm: Memory Power Management References: <20130925231250.26184.31438.stgit@srivatsabhat.in.ibm.com> <52437128.7030402@linux.vnet.ibm.com> <20130925164057.6bbaf23bdc5057c42b2ab010@linux-foundation.org> <20130925234734.GK18242@two.firstfloor.org> In-Reply-To: <20130925234734.GK18242@two.firstfloor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 963 Lines: 21 On 9/25/2013 4:47 PM, Andi Kleen wrote: >> Also, the changelogs don't appear to discuss one obvious downside: the >> latency incurred in bringing a bank out of one of the low-power states >> and back into full operation. Please do discuss and quantify that to >> the best of your knowledge. > > On Sandy Bridge the memry wakeup overhead is really small. It's on by default > in most setups today. yet grouping is often defeated (in current systems) due to hw level interleaving ;-( sometimes that's a bios setting though. in internal experimental bioses we've been able to observe a "swing" of a few watts (not with these patches but with some other tricks)... I'm curious to see how these patches do for Srivatsa -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/