linux-kernel - Re: [PATCH 13/15] sched: Set preferred NUMA node based on number of private faults

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20130706104446.GS18898@dyad.programming.kicks-ass.net>
Date:	Sat, 6 Jul 2013 12:44:46 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Mel Gorman <mgorman@...e.de>
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 13/15] sched: Set preferred NUMA node based on number of
 private faults

On Sat, Jul 06, 2013 at 12:09:00AM +0100, Mel Gorman wrote:
> The third reason is that multiple threads in a process will race each
> other to fault the shared page making the fault information unreliable.

Ingo and I played around with that particular issue for a while and we had a
patch that worked fairly well for cpu bound threads and made sure the
task_numa_work() thing indeed interleaved between the threads and wasn't done
by the same thread every time.

I don't know what the current code does and if that is indeed still an issue.
--
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/