From: Peter Zijlstra <peterz@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: dedekind1@gmail.com, linux-kernel@vger.kernel.org,
mgorman@suse.de, jhladky@redhat.com
Subject: Re: [PATCH] numa,sched: only consider less busy nodes as numa balancing destination
Date: Wed, 13 May 2015 08:31:06 +0200 [thread overview]
Message-ID: <20150513063106.GA1156@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20150513062906.GJ3007@worktop.Skamania.guest>
On Wed, May 13, 2015 at 08:29:06AM +0200, Peter Zijlstra wrote:
> @@ -1572,9 +1582,10 @@ static void numa_migrate_preferred(struct task_struct *p)
> * are added when they cause over 6/16 of the maximum number of faults, but
> * only removed when they drop below 3/16.
> */
> -static void update_numa_active_node_mask(struct numa_group *numa_group)
> +static bool update_numa_active_node_mask(struct numa_group *numa_group)
> {
> unsigned long faults, max_faults = 0;
> + bool update = false;
> int nid;
>
> for_each_online_node(nid) {
> @@ -1586,11 +1597,17 @@ static void update_numa_active_node_mask(struct numa_group *numa_group)
> for_each_online_node(nid) {
> faults = group_faults_cpu(numa_group, nid);
> if (!node_isset(nid, numa_group->active_nodes)) {
> - if (faults > max_faults * 6 / 16)
> + if (faults > max_faults * 6 / 16) {
> node_set(nid, numa_group->active_nodes);
> - } else if (faults < max_faults * 3 / 16)
> + update = true;
> + }
> + } else if (faults < max_faults * 3 / 16) {
> node_clear(nid, numa_group->active_nodes);
> + update = true;
> + }
> }
> +
> + return update;
> }
>
> /*
Ignore these hunks, they're dead wood.
next prev parent reply other threads:[~2015-05-13 6:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 10:35 autoNUMA web workload regression Artem Bityutskiy
2015-05-06 10:37 ` Bityutskiy, Artem
2015-05-06 14:40 ` Rik van Riel
2015-05-06 15:41 ` [PATCH] numa,sched: only consider less busy nodes as numa balancing destination Rik van Riel
2015-05-06 17:00 ` Peter Zijlstra
2015-05-06 17:06 ` Rik van Riel
2015-05-07 13:29 ` Artem Bityutskiy
2015-05-08 13:13 ` Artem Bityutskiy
2015-05-08 20:03 ` Rik van Riel
2015-05-08 22:52 ` Rik van Riel
2015-05-11 11:11 ` Artem Bityutskiy
2015-05-11 14:20 ` Rik van Riel
2015-05-12 13:50 ` Artem Bityutskiy
2015-05-12 15:45 ` Rik van Riel
2015-05-13 6:29 ` Peter Zijlstra
2015-05-13 6:31 ` Peter Zijlstra [this message]
2015-05-13 10:59 ` Artem Bityutskiy
2015-05-13 13:51 ` Rik van Riel
2015-05-11 12:44 ` Jirka Hladky
2015-05-11 14:44 ` Rik van Riel
2015-05-26 20:29 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150513063106.GA1156@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=dedekind1@gmail.com \
--cc=jhladky@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox