From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755061Ab2CSLbV (ORCPT ); Mon, 19 Mar 2012 07:31:21 -0400 Received: from merlin.infradead.org ([205.233.59.134]:43723 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751899Ab2CSLbU convert rfc822-to-8bit (ORCPT ); Mon, 19 Mar 2012 07:31:20 -0400 Message-ID: <1332156655.18960.297.camel@twins> Subject: Re: [RFC][PATCH 00/26] sched/numa From: Peter Zijlstra To: Avi Kivity Cc: Linus Torvalds , Andrew Morton , Thomas Gleixner , Ingo Molnar , Paul Turner , Suresh Siddha , Mike Galbraith , "Paul E. McKenney" , Lai Jiangshan , Dan Smith , Bharata B Rao , Lee Schermerhorn , Andrea Arcangeli , Rik van Riel , Johannes Weiner , linux-kernel@vger.kernel.org, linux-mm@kvack.org Date: Mon, 19 Mar 2012 12:30:55 +0100 In-Reply-To: <1332155527.18960.292.camel@twins> References: <20120316144028.036474157@chello.nl> <4F670325.7080700@redhat.com> <1332155527.18960.292.camel@twins> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2012-03-19 at 12:12 +0100, Peter Zijlstra wrote: > Also, if you go scan memory, you need some storage -- see how aa grows > struct page, sure he wants to move that storage some place else, but the > memory overhead is still there -- this means less memory to actually do > useful stuff in (it also probably means more cache-misses since his > proposed shadow array in pgdat is someplace else). Going by the sizes in aa's patch, that's 96M of my 16G box gone. That puts HPC people in a rather awkward position of having to choose between more memory and slightly smarter kernel. I'm thinking they're going to opt for going the way they are now (hard affinity/userspace balancers) and use the extra memory. This even though typical MPI implementations use the multi-process scheme, so the simple home-node approach I used works just fine for them.