From: Peter Zijlstra <peterz@infradead.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org, chegu_vinod@hp.com,
mingo@kernel.org, umgwanakikbuti@gmail.com
Subject: Re: [PATCH RFC] sched,numa: move tasks to preferred_node at wakeup time
Date: Fri, 16 May 2014 15:38:05 +0200 [thread overview]
Message-ID: <20140516133805.GS11096@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140516021450.473361ea@annuminas.surriel.com>
[-- Attachment #1: Type: text/plain, Size: 2445 bytes --]
On Fri, May 16, 2014 at 02:14:50AM -0400, Rik van Riel wrote:
> +#ifdef CONFIG_NUMA_BALANCING
> +static int numa_balance_on_wake(struct task_struct *p, int prev_cpu)
> +{
> + long load, src_load, dst_load;
> + int cur_node = cpu_to_node(prev_cpu);
> + struct numa_group *numa_group = ACCESS_ONCE(p->numa_group);
> + struct sched_domain *sd;
> + struct task_numa_env env = {
> + .p = p,
> + .best_task = NULL,
> + .best_imp = 0,
> + .best_cpu = -1
> + };
That's all code, ideally you'd move that after we're done checking the
reasons to not do work, say somehere like...
> +
> + if (!sched_feat(NUMA))
> + return prev_cpu;
Yah.. :-( I think some people changed that to numabalancing_enabled.
Fixing that is still on the todo list somewhere.
> +
> + if (p->numa_preferred_nid == -1)
> + return prev_cpu;
> +
> + if (p->numa_preferred_nid == cur_node);
> + return prev_cpu;
> +
> + if (numa_group && node_isset(cur_node, numa_group->active_nodes))
> + return prev_cpu;
> +
> + sd = rcu_dereference(per_cpu(sd_numa, env.src_cpu));
> + if (sd)
> + env.imbalance_pct = 100 + (sd->imbalance_pct - 100) / 2;
> +
> + /*
> + * Cpusets can break the scheduler domain tree into smaller
> + * balance domains, some of which do not cross NUMA boundaries.
> + * Tasks that are "trapped" in such domains cannot be migrated
> + * elsewhere, so there is no point in (re)trying.
> + */
> + if (unlikely(!sd)) {
How about you bail early, and then have the above test evaporate?
> + p->numa_preferred_nid = cur_node;
> + return prev_cpu;
> + }
.. here.
> +
> + /*
> + * Only allow p to move back to its preferred nid if
> + * that does not create an imbalance that would cause
> + * the load balancer to move a task around later.
> + */
> + env.src_nid = cur_node;
> + env.dst_nid = p->numa_preferred_nid;
> +
> + update_numa_stats(&env.src_stats, env.src_nid);
> + update_numa_stats(&env.dst_stats, env.dst_nid);
> +
> + dst_load = env.dst_stats.load;
> + src_load = env.src_stats.load;
> +
> + /* XXX missing power terms */
> + load = task_h_load(p);
> + dst_load += load;
> + src_load -= load;
> +
> + if (load_too_imbalanced(env.src_stats.load, env.dst_stats.load,
> + src_load, dst_load, &env))
> + return prev_cpu;
So I'm thinking that load_too_imbalanced() is from another patch I
haven't yet seen, lemme go see if you did send it and I missed it.
> +
> + return cpumask_first(cpumask_of_node(p->numa_preferred_nid));
> +}
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-16 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 4:13 [PATCH RFC] sched,numa: decay wakee_flips instead of zeroing Rik van Riel
2014-05-16 6:14 ` [PATCH RFC] sched,numa: move tasks to preferred_node at wakeup time Rik van Riel
2014-05-16 13:38 ` Peter Zijlstra [this message]
2014-05-16 13:22 ` [PATCH RFC] sched,numa: decay wakee_flips instead of zeroing Peter Zijlstra
2014-05-19 13:11 ` [tip:sched/core] sched,numa: Decay " tip-bot for Rik van Riel
2014-05-22 12:29 ` [tip:sched/core] sched/numa: Decay -> " tip-bot for 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=20140516133805.GS11096@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=chegu_vinod@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=umgwanakikbuti@gmail.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