linux-kernel - Re: [PATCH 08/16] sched: Reschedule task on preferred NUMA node once selected

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 12 Jul 2013 11:28:19 +0100
From:	Mel Gorman <mgorman@...e.de>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	Ingo Molnar <mingo@...nel.org>,
	Andrea Arcangeli <aarcange@...hat.com>,
	Johannes Weiner <hannes@...xchg.org>,
	Linux-MM <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 08/16] sched: Reschedule task on preferred NUMA node once
 selected

On Fri, Jul 12, 2013 at 12:14:08PM +0200, Peter Zijlstra wrote:
> On Thu, Jul 11, 2013 at 03:09:14PM +0100, Mel Gorman wrote:
> > That might be necessary when the machine is overloaded. As a
> > starting point the following should retry the migrate a number of times
> > until success. The retry is checked on every fault but should not fire
> > more than once every 100ms.
>  
> Yeah, something like that might work. But getting a working imbalance bound is
> important. The current very weak direct migration is the only thing that keeps
> the system from massively skewing load.

I've corrected a flaw in that proposed patch, pulled in the check for
dst load vs src load, and am adding another patch that will fallback to
less preferred nodes if task_numa_find_cpu fails to find a suitable CPU.

-- 
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/