From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) by kanga.kvack.org (Postfix) with ESMTP id 396FC6B0037 for ; Thu, 26 Sep 2013 15:38:27 -0400 (EDT) Received: by mail-pb0-f46.google.com with SMTP id rq2so1555210pbb.5 for ; Thu, 26 Sep 2013 12:38:26 -0700 (PDT) Date: Thu, 26 Sep 2013 21:38:22 +0200 From: Andi Kleen Subject: Re: [Results] [RFC PATCH v4 00/40] mm: Memory Power Management Message-ID: <20130926193822.GO18242@two.firstfloor.org> References: <20130925231250.26184.31438.stgit@srivatsabhat.in.ibm.com> <52437128.7030402@linux.vnet.ibm.com> <20130925164057.6bbaf23bdc5057c42b2ab010@linux-foundation.org> <52442F6F.5020703@linux.vnet.ibm.com> <3908561D78D1C84285E8C5FCA982C28F31D1B6BE@ORSMSX106.amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3908561D78D1C84285E8C5FCA982C28F31D1B6BE@ORSMSX106.amr.corp.intel.com> Sender: owner-linux-mm@kvack.org List-ID: To: "Luck, Tony" Cc: "Srivatsa S. Bhat" , Andrew Morton , "mgorman@suse.de" , "dave@sr71.net" , "hannes@cmpxchg.org" , "matthew.garrett@nebula.com" , "riel@redhat.com" , "arjan@linux.intel.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" , "andi@firstfloor.org" , "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" , "maxime.coquelin@stericsson.com" , "loic.pallardy@stericsson.com" , "amit.kachhap@linaro.org" , "thomas.abraham@linaro.org" > The interleave problem mentioned elsewhere in this thread is possibly a big problem. > High core counts mean that memory bandwidth can be the bottleneck for several > workloads. Dropping, or reducing, the degree of interleaving will seriously impact > bandwidth (unless your applications are spread out "just right"). In practice this doesn't seem to be that big a problem. I think because most very memory intensive workloads, use all the memory from all the cores, so they effectively interleave by themselves. -Andi -- ak@linux.intel.com -- Speaking for myself only. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org