Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753010Ab2KWPXM (ORCPT ); Fri, 23 Nov 2012 10:23:12 -0500 Received: from mail-ob0-f174.google.com ([209.85.214.174]:52312 "EHLO mail-ob0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752521Ab2KWPXK (ORCPT ); Fri, 23 Nov 2012 10:23:10 -0500 MIME-Version: 1.0 In-Reply-To: <20121123133138.GA28058@gmail.com> References: <20121119162909.GL8218@suse.de> <20121119191339.GA11701@gmail.com> <20121119211804.GM8218@suse.de> <20121119223604.GA13470@gmail.com> <20121120071704.GA14199@gmail.com> <20121120152933.GA17996@gmail.com> <20121120175647.GA23532@gmail.com> <20121122012122.GA7938@gmail.com> <20121123133138.GA28058@gmail.com> Date: Fri, 23 Nov 2012 23:23:09 +0800 Message-ID: Subject: Re: numa/core regressions fixed - more testers wanted From: Alex Shi To: Ingo Molnar Cc: Linus Torvalds , David Rientjes , Mel Gorman , Linux Kernel Mailing List , linux-mm , Peter Zijlstra , Paul Turner , Lee Schermerhorn , Christoph Lameter , Rik van Riel , Andrew Morton , Andrea Arcangeli , Thomas Gleixner , Johannes Weiner , Hugh Dickins , Alex Shi Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2216 Lines: 68 On Fri, Nov 23, 2012 at 9:31 PM, Ingo Molnar wrote: > > * Ingo Molnar wrote: > >> * Alex Shi wrote: >> >> > > >> > > Those of you who would like to test all the latest patches are >> > > welcome to pick up latest bits at tip:master: >> > > >> > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master >> > > >> > >> > I am wondering if it is a problem, but it still exists on HEAD: c418de93e39891 >> > http://article.gmane.org/gmane.linux.kernel.mm/90131/match=compiled+with+name+pl+and+start+it+on+my >> > >> > like when just start 4 pl tasks, often 3 were running on node >> > 0, and 1 was running on node 1. The old balance will average >> > assign tasks to different node, different core. >> >> This is "normal" in the sense that the current mainline >> scheduler is (supposed to be) doing something similar: if the >> node is still within capacity, then there's no reason to move >> those threads. >> >> OTOH, I think with NUMA balancing we indeed want to spread >> them better, if those tasks do not share memory with each >> other but use their own memory. If they share memory then they >> should remain on the same node if possible. There is no share memory between them. > > Could you please check tip:master with -v17: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master > > ? > > It should place your workload better than v16 did. OK. will try it on next Monday, if it is not late to you. > > Note, you might be able to find other combinations of tasks that > are not scheduled NUMA-perfectly yet, as task group placement is > not exhaustive yet. I am not familiar with task group. but anyway, will try it too. > > You might want to check which combination looks the weirdest to > you and report it, so I can fix any remaining placement > inefficiencies in order of importance. Any suggestions of combination? > > Thanks, > > Ingo -- Thanks Alex -- 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/