Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965122Ab3IELPS (ORCPT ); Thu, 5 Sep 2013 07:15:18 -0400 Received: from mail-ea0-f181.google.com ([209.85.215.181]:61977 "EHLO mail-ea0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756011Ab3IELPQ (ORCPT ); Thu, 5 Sep 2013 07:15:16 -0400 Date: Thu, 5 Sep 2013 13:15:10 +0200 From: Ingo Molnar To: Alex Thorlton Cc: Robin Holt , "Kirill A. Shutemov" , Dave Hansen , linux-kernel@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Andrew Morton , Mel Gorman , "Kirill A . Shutemov" , Rik van Riel , Johannes Weiner , "Eric W . Biederman" , Sedat Dilek , Frederic Weisbecker , Dave Jones , Michael Kerrisk , "Paul E . McKenney" , David Howells , Thomas Gleixner , Al Viro , Oleg Nesterov , Srikar Dronamraju , Kees Cook Subject: Re: [PATCH 1/8] THP: Use real address for NUMA policy Message-ID: <20130905111510.GC23362@gmail.com> References: <87wqo050fc.fsf@tassilo.jf.intel.com> <1376663644-153546-1-git-send-email-athorlton@sgi.com> <1376663644-153546-2-git-send-email-athorlton@sgi.com> <520E672C.3080102@intel.com> <20130816181728.GQ26093@sgi.com> <20130816185212.GA3568@shutemov.name> <20130827165039.GC2886@sgi.com> <20130904154301.GA2975@sgi.com> <20130904171528.GB2975@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130904171528.GB2975@sgi.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 984 Lines: 27 * Alex Thorlton wrote: > > Robin, > > > > I tweaked one of our other tests to behave pretty much exactly as I > > - malloc a large array > > - Spawn a specified number of threads > > - Have each thread touch small, evenly spaced chunks of the array (e.g. > > for 128 threads, the array is divided into 128 chunks, and each thread > > touches 1/128th of each chunk, dividing the array into 16,384 pieces) > > Forgot to mention that the threads don't touch their chunks of memory > concurrently, i.e. thread 2 has to wait for thread 1 to finish first. > This is important to note, since the pages won't all get stuck on the > first node without this behavior. Could you post the testcase please? Thanks, Ingo -- 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/