From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756191AbbFRRBB (ORCPT ); Thu, 18 Jun 2015 13:01:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49271 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754188AbbFRRAy (ORCPT ); Thu, 18 Jun 2015 13:00:54 -0400 Message-ID: <5582F944.6080204@redhat.com> Date: Thu, 18 Jun 2015 13:00:52 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Srikar Dronamraju CC: linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@kernel.org, mgorman@suse.de Subject: Re: [PATCH] sched,numa: document and fix numa_preferred_nid setting References: <20150616155450.62ec234b@cuia.usersys.redhat.com> <20150618155547.GA16576@linux.vnet.ibm.com> <5582EC99.8040005@redhat.com> <20150618164140.GB16576@linux.vnet.ibm.com> In-Reply-To: <20150618164140.GB16576@linux.vnet.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/18/2015 12:41 PM, Srikar Dronamraju wrote: > * Rik van Riel [2015-06-18 12:06:49]: > >>>> >>> >>> Overall this patch does seem to produce better results. However numa02 >>> gets affected -vely. >> >> OK, that is kind of expected. >> >> The way numa02 runs means that we are essentially guaranteed >> that, on a two node system, both nodes end up in the numa_group's >> active_mask. >> > > Just to add this was on a 4 node machine. OK, so we are looking at two multi-threaded processes on a 4 node system, and waiting for them to converge? It may make sense to add my patch in with your patch 1/4 from last week, as well as the correct part of your patch 4/4, and see how they all work together.