Re: [PATCH 9/7] sched,numa: remove task_h_load from task_numa_compare

[Rik van Riel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/25/2014 01:31 AM, Peter Zijlstra wrote:
> On Wed, Jun 25, 2014 at 01:25:00AM -0400, Rik van Riel wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> On 06/25/2014 01:21 AM, Peter Zijlstra wrote:
>>> On Wed, Jun 25, 2014 at 07:07:35AM +0200, Peter Zijlstra
>>> wrote:
>>>> Shall I merge this into patch 3?
>>> 
>>> Which gets me the below; which is has a wrong changelog.
>>> 
>>> task_h_load() already computes the load as seen from the root 
>>> group. effective_load() just does a better (and more expensive)
>>> job of computing the task movement implications of a move.
>>> 
>>> So the total effect of this patch shouldn't be very big;
>>> regular load balancing also only uses task_h_load(), see
>>> move_tasks().
>>> 
>>> Now, we don't run with preemption disabled, don't run as
>>> often, etc.., so maybe we can indeed use the more expensive
>>> variant just fine, but does it really matter?
>> 
>> In my testing, it appears to make a difference between workloads 
>> converging, and workloads sitting with one last thread stuck on 
>> another node that never gets moved...
> 
> Fair enough; can you provide a new Changelog that I can paste in?

Here it goes:

When CONFIG_FAIR_GROUP_SCHED is enabled, the load that a task places
on a CPU is determined by the group the task is in. The active groups
on the source and destination CPU can be different, resulting in a
different load contribution by the same task at its source and at its
destination. As a result, the load needs to be calculated separately
for each CPU, instead of estimated once with task_h_load.

Getting this calculation right allows some workloads to converge,
where previously the last thread could get stuck on another node,
without being able to migrate to its final destination.




- -- 
All rights reversed
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTqmCPAAoJEM553pKExN6D4/IH/1Ez7G3jAnYFpQYvH/wSm75V
kbH+mouLAqeICjHRdXAr1SGuD8i85JeUeDU2+SymdhC+hwZXbvR/aQfX0/ok4kN7
e7kJbaNS6Lrq3bDjm74aTpMKB+zK2OExqR1DQBXwynbUahAyx3+9uXNDYp35yZwo
tt+h3Rdrmy2lTTpE0fuEjGc8ODrEJjeWyYAVxT/aQXnwgfXfp6BZ1SEXyRRmrxR0
BunsgWTO7uBxGGEIZrrm/l7mdIrsi4oAN9C4RA7v6LMR6cUW9Fj5o6iva9X714wG
txP4/AGowucS5VckN1RIaM8/pzMB3MVuAmCTX4PqWg1jf3eggcQpe5/4/bVYUqQ=
=QgYM
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/