linux-kernel - Re: [PATCH 1/7] sched,numa: use group's max nid as task's preferred nid

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140625103149.GZ10819@suse.de>
Date:	Wed, 25 Jun 2014 11:31:49 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	riel@...hat.com
Cc:	linux-kernel@...r.kernel.org, chegu_vinod@...com,
	peterz@...radead.com, mingo@...nel.org
Subject: Re: [PATCH 1/7] sched,numa: use group's max nid as task's preferred
 nid

On Mon, Jun 23, 2014 at 11:41:29AM -0400, riel@...hat.com wrote:
> From: Rik van Riel <riel@...hat.com>
> 
> From task_numa_placement, always try to consolidate the tasks
> in a group on the group's top nid.
> 
> In case this task is part of a group that is interleaved over
> multiple nodes, task_numa_migrate will set the task's preferred
> nid to the best node it could find for the task, so this patch
> will cause at most one run through task_numa_migrate.
> 
> Signed-off-by: Rik van Riel <riel@...hat.com>

That loop was written prior to pseudo-interleaving as well and in the
context of that change this makes sense and removes a potentially
expensive loop.

Acked-by: Mel Gorman <mgorman@...e.de>

-- 
Mel Gorman
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/