From: Mike Galbraith <efault@gmx.de>
To: Mel Gorman <mgorman@techsingularity.net>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Matt Fleming <matt@codeblueprint.co.uk>
Subject: Re: [PATCH] sched: Only migrate tasks due to interrupts on an idle CPU if prev and target CPUs share cache
Date: Fri, 15 Dec 2017 21:38:06 +0100 [thread overview]
Message-ID: <1513370286.11185.136.camel@gmx.de> (raw)
In-Reply-To: <20171215165241.ckrs7c6zobjj6rcx@techsingularity.net>
On Fri, 2017-12-15 at 16:52 +0000, Mel Gorman wrote:
>
> It's a small improvement...
>From my log on corr.arch.suse.de (2x8 box)
4.15.0.g2db767d-default
Throughput 2665.88 MB/sec 8 clients 8 procs max_latency=21.472 ms
4.15.0.g2db767d-default NO_WA_IDLE
Throughput 3416.35 MB/sec 8 clients 8 procs max_latency=9.825 ms
Not so small improvement. WA_IDLE ripped corr up pretty bad, turning
it off restored 4.4 performance.
>
> Signed-off-by: Mel Gorman <mgorman@techsingularity.net>
> ---
> kernel/sched/fair.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 2fe3aa853e4d..4a1f7d32ecf6 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -5701,7 +5701,13 @@ static bool
> wake_affine_idle(struct sched_domain *sd, struct task_struct *p,
> int this_cpu, int prev_cpu, int sync)
> {
> - if (idle_cpu(this_cpu))
> + /*
> + * If this_cpu is idle, it implies the wakeup is from interrupt
> + * context. Only allow the move if cache is shared. Otherwise an
> + * interrupt intensive workload could force all tasks onto one
> + * node depending on the IO topology or IRQ affinity settings.
> + */
> + if (idle_cpu(this_cpu) && cpus_share_cache(this_cpu, prev_cpu))
> return true;
>
> if (sync && cpu_rq(this_cpu)->nr_running == 1)
next prev parent reply other threads:[~2017-12-15 20:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 16:52 Mel Gorman
2017-12-15 20:38 ` Mike Galbraith [this message]
2017-12-16 18:28 ` Mel Gorman
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=1513370286.11185.136.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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
Powered by JetHome