linux-kernel - Re: [PATCH] sched,numa: document and fix numa_preferred

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]

Date:	Thu, 18 Jun 2015 13:00:52 -0400
From:	Rik van Riel <riel@...hat.com>
To:	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
CC:	linux-kernel@...r.kernel.org, peterz@...radead.org,
	mingo@...nel.org, mgorman@...e.de
Subject: Re: [PATCH] sched,numa: document and fix numa_preferred_nid setting

On 06/18/2015 12:41 PM, Srikar Dronamraju wrote:
> * Rik van Riel <riel@...hat.com> [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.
--
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/