From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756770Ab3JGTOZ (ORCPT ); Mon, 7 Oct 2013 15:14:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:55868 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752891Ab3JGTOW (ORCPT ); Mon, 7 Oct 2013 15:14:22 -0400 Message-ID: <52530800.1070902@redhat.com> Date: Mon, 07 Oct 2013 15:14:08 -0400 From: Rik van Riel User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Mel Gorman CC: Peter Zijlstra , Srikar Dronamraju , Ingo Molnar , Andrea Arcangeli , Johannes Weiner , Linux-MM , LKML Subject: Re: [PATCH 55/63] sched: numa: Avoid migrating tasks that are placed on their preferred node References: <1381141781-10992-1-git-send-email-mgorman@suse.de> <1381141781-10992-56-git-send-email-mgorman@suse.de> In-Reply-To: <1381141781-10992-56-git-send-email-mgorman@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/07/2013 06:29 AM, Mel Gorman wrote: > From: Peter Zijlstra > > This patch classifies scheduler domains and runqueues into types depending > the number of tasks that are about their NUMA placement and the number > that are currently running on their preferred node. The types are > > regular: There are tasks running that do not care about their NUMA > placement. > > remote: There are tasks running that care about their placement but are > currently running on a node remote to their ideal placement > > all: No distinction > > To implement this the patch tracks the number of tasks that are optimally > NUMA placed (rq->nr_preferred_running) and the number of tasks running > that care about their placement (nr_numa_running). The load balancer > uses this information to avoid migrating idea placed NUMA tasks as long > as better options for load balancing exists. For example, it will not > consider balancing between a group whose tasks are all perfectly placed > and a group with remote tasks. > > Signed-off-by: Peter Zijlstra > Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel -- All rights reversed From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com [209.85.192.174]) by kanga.kvack.org (Postfix) with ESMTP id 70ECF6B0036 for ; Mon, 7 Oct 2013 15:14:20 -0400 (EDT) Received: by mail-pd0-f174.google.com with SMTP id y13so7689346pdi.33 for ; Mon, 07 Oct 2013 12:14:20 -0700 (PDT) Message-ID: <52530800.1070902@redhat.com> Date: Mon, 07 Oct 2013 15:14:08 -0400 From: Rik van Riel MIME-Version: 1.0 Subject: Re: [PATCH 55/63] sched: numa: Avoid migrating tasks that are placed on their preferred node References: <1381141781-10992-1-git-send-email-mgorman@suse.de> <1381141781-10992-56-git-send-email-mgorman@suse.de> In-Reply-To: <1381141781-10992-56-git-send-email-mgorman@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Mel Gorman Cc: Peter Zijlstra , Srikar Dronamraju , Ingo Molnar , Andrea Arcangeli , Johannes Weiner , Linux-MM , LKML On 10/07/2013 06:29 AM, Mel Gorman wrote: > From: Peter Zijlstra > > This patch classifies scheduler domains and runqueues into types depending > the number of tasks that are about their NUMA placement and the number > that are currently running on their preferred node. The types are > > regular: There are tasks running that do not care about their NUMA > placement. > > remote: There are tasks running that care about their placement but are > currently running on a node remote to their ideal placement > > all: No distinction > > To implement this the patch tracks the number of tasks that are optimally > NUMA placed (rq->nr_preferred_running) and the number of tasks running > that care about their placement (nr_numa_running). The load balancer > uses this information to avoid migrating idea placed NUMA tasks as long > as better options for load balancing exists. For example, it will not > consider balancing between a group whose tasks are all perfectly placed > and a group with remote tasks. > > Signed-off-by: Peter Zijlstra > Signed-off-by: Mel Gorman Reviewed-by: Rik van Riel -- All rights reversed -- 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